MCP Gateway · Claude Code
Connect Supabase to Claude Code
Claude Code can work on your Supabase database from the terminal, reading the schema, writing migrations and checking logs when something breaks. With Supabase behind the Speakeasy MCP Gateway, a developer's role decides which of its tools Claude Code may call, and each change it makes is recorded under that developer's name.
- Category
- Data & analytics
- Tools
- 29
- Authentication
- OAuth
- Claude Code
- CLI
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 Code 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 Code
Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.
Run the command below with your organization gateway URL.
Open
/mcpin Claude Code and choose Authenticate to sign in.claude mcp add --transport http --scope user \ 'speakeasy' \ 'https://<organization host>/mcp/gateway/<organization slug>' - 04
Sign in and use Supabase from Claude Code
The first time Claude Code 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 Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.
Use cases
What Claude Code users do with Supabase
Write a migration from the real schema
Claude Code lists the tables with column details and the migrations already applied, then applies a new migration for the schema change you describe.
Debug an API error from logs
When a request to your backend fails, Claude Code pulls the last day of logs for the service involved and matches the error to the code that made the call.
Regenerate types after a schema change
After a migration, Claude Code regenerates the project's TypeScript types so your client code compiles against the new columns and tables.
Tools
29 tools
Each Supabase tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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 Code
The gateway covers every client the same way. The rest depends on what Claude Code 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 Code. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Claude Code
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.
User attribution
Claude Code
Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.
Budgets
Claude Code
Spend limits can block Claude Code traffic once a budget is reached.
Device agent and MDM
Claude Code
The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.
Anthropic inference hooks
Claude Code
On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).
- Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
- Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.
Questions
Frequently asked questions
Can I stop Claude Code from running raw SQL on Supabase?
How are Supabase changes from Claude Code tied to a person?
How do Claude Code users get Supabase?
Are Supabase calls from Claude Code logged?
Connect more