MCP Gateway · Claude
Connect Supabase to Claude
Product and operations people can ask Claude about the data and projects in Supabase without writing code. Through the Speakeasy MCP Gateway, each person connects once from Customize > Connectors and reaches only the Supabase tools their role allows, so a read-only role stays read-only.
- Category
- Data & analytics
- Tools
- 29
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run Supabase MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Supabase call inspected and logged.
Set up
Add Supabase to Claude in 4 steps
- 01
Add Supabase from the catalog
An admin finds Supabase in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Supabase uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Supabase
Give teams the
mcp:connectscope on the Supabase server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Supabase to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Supabase from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Supabase needs its own OAuth grant, so each person connects it once. Until they do, Supabase calls fail while the rest of the gateway keeps working.
From then on, Supabase's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Supabase
Answer a question from the database
Ask how many sign-ups came in this week, and Claude runs a query against the Postgres database and explains the answer in a sentence.
Check plans and projects before budgeting
Claude looks up the organization's subscription plan and the details of each project, so you know what is running before a budget review.
Learn how a Supabase feature works
Claude searches the Supabase documentation and explains a feature such as branching in plain terms before you discuss it with engineering.
Tools
29 tools
Each Supabase tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
search_docs
Search the Supabase documentation using GraphQL. Must be a valid GraphQL query. You should default to calling this even if you think you already know the answer, since the documentation is always being updated.
list_organizations
Lists all organizations that the user is a member of.
get_organization
Gets details for an organization. Includes subscription plan.
list_projects
Lists all Supabase projects for the user. Use this to help discover the project ID of the project that the user is working on.
get_project
Gets details for a Supabase project.
get_cost
Gets the cost of creating a new project or branch. Never assume organization as costs can be different for each. Always repeat the cost to the user and confirm their understanding before proceeding.
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every Supabase call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Supabase tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Supabase can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can Supabase conversations in Claude be reviewed later?
Do Speakeasy budgets cover Supabase use in Claude?
How do Claude users get Supabase?
Are Supabase calls from Claude logged?
Connect more