CHUMBO RECIPES

Go further

Add interactive Apps, multiple servers, observability or durable state when your application needs them.

Show callers what they can use. Reject what they cannot. ↗

Serve different capability sets from one MCP using application-resolved scopes, with authorization on discovery and direct calls.

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.

MCP Apps

Open a useful interface. Keep the action inside MCP. ↗

Serve a bundled interactive MCP App through one Supabase Edge Function while host-mediated tools preserve the caller's auth, scopes, and RLS boundary.

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 ↗