CHUMBO RECIPES

Test and ship

Check your advertised capabilities, real access behavior and deployment before inviting users.

A coding agent with the right context builds the right MCP. ↗

Install project-local Chumbo guidance, preview setup changes and give a coding agent a bounded application task it can verify.

Authentication & access

Let agents into your app. Keep your permissions. ↗

Let your users’ agents work with their projects. Chumbo connects the MCP layer to Supabase Auth, so your existing row-level security stays in charge.

Result design

Ten rows and a cursor beat a thousand rows and a timeout. ↗

Return compact project pages from your Supabase MCP, with bounded results, stable cursors, and a clear next call for agents and typed clients.

Application actions

One narrow write, and a receipt for what changed. ↗

Wrap an existing application write in a narrow MCP tool and return a compact receipt with the resulting state and next step.

Capability tests

Test the boundary your callers will hit, not just the code behind it. ↗

Exercise the Chumbo MCP boundary with controlled dependencies, then keep real Supabase authentication and RLS checks as a separate integration layer.

Deployment and debugging

Does the deployed endpoint answer the call your users will make? ↗

Move from local checks to an actual MCP call, diagnose the failing boundary and verify the deployed endpoint your users will connect to.

Product URLs

Put your MCP at your app’s URL. Keep Supabase behind it. ↗

Expose your existing MCP at a product-facing URL while preserving the function route, OAuth metadata and request behavior.

Multiple MCPs

Serve several MCPs. Deploy one Edge Function. ↗

Resolve a named MCP from the request path, give each surface its own instructions and capabilities, and keep one deployable Supabase Edge Function.

Durable state

Remember what a caller observed. Fail closed when it changes. ↗

Use Chumbo's bounded credential-partitioned state for read-before-write receipts while application RLS and resource versions remain authoritative.

Observability

What did the MCP just do? Now you can answer. ↗

Record redacted capability lifecycle facts, capture the advertised tool surface, and join selected calls into an explicit application run.

Read it. Try it. Make it yours.

Every recipe includes the example, its prerequisites, expected checks, and source links. Open the Markdown or copy the instructions for your coding agent. Your application remains the authority on its users and data.

Start with the Chumbo guide ↗