CHUMBO RECIPES

Connect users

Choose a connection that fits your users and preserves your application’s permissions.

Start with who is connecting. Choose auth from there. ↗

Choose the Chumbo access mode that fits your callers, with a clear account of which identity reaches your Supabase data.

OAuth connections

Let users connect their accounts. Keep your app’s sign-in. ↗

Give users a sign-in and consent path to your Supabase MCP, then verify the account and permissions behind a real tool call.

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.

Scoped capabilities

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.

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.

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.

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 ↗