MCP made easy on Supabase.

Connect your Supabase app to agents with one guided setup. Chumbo handles the MCP layer. You choose what agents can do.

See how setup works
Chumbo works with
what you built
One guided setupstart from the project you already have
Your app stays in chargeyou choose what agents can do
Room to growadvanced patterns stay optional

From your Supabase project to something agents can use.

Chumbo keeps the path small. Run setup, add the useful action your product needs, then deploy one Edge Function.

01

Run guided setup

Chumbo inspects your project, asks who may connect, and previews every file before it writes anything.

npx chumbo setup
02

Choose what agents can do

Add the actions your product needs in the generated capabilities.ts. Start with one useful thing.

03

Deploy with Supabase

Deploy the generated function, connect your MCP client, and use Chumbo's doctor command to check the result.

Your software already has a body. Chumbo gives it hands.

Your app remains the source of truth. Chumbo adds the connection agents need without replacing the product behind it.

Your app. Now MCP.

The rules you already set still apply.

Your existing sign-in and data rules decide who can connect and what they may reach. Chumbo carries those rules into agent requests instead of creating a second user system.

Alice · Claudelist_projects()her rows only
Bob · Cursorlist_projects()his rows only
Supabase AuthRLSPostgres
Verified

Start simple. Grow without starting over.

The first path stays small. When your product needs more, the same Chumbo server can add user sign-in, tighter capability boundaries, richer MCP surfaces, and advanced patterns.

Auth stays yours
For your users

Let each person connect their own account.

OAuth can carry their existing Supabase identity and rules.

For tighter boundaries

Show callers only the capabilities they can use.

Scopes can shape what each connection discovers.

For richer MCPs

Use tools, resources, prompts, and multi-step flows.

The official MCP surface remains available as you grow.

For advanced work

Add durable state and living patterns only when needed.

The default path stays stateless and small.

Explore the technical guide →
An MCP endpoint becoming a pointing hand

Give your app hands.

One guided setup puts the connection in place. What those hands can do is yours to design.