Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Supabase to Claude Code

Let Claude run scoped reads and writes against your Supabase data. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Supabase to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Supabase, you add a Supabase MCP server: a small hosted service that exposes Supabase's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Supabase account. No API keys pasted into config files.

claude mcp add --transport http supabase https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Supabase once connected?

Full read-write Supabase access lets Claude insert and update rows, run parameterized queries, apply migrations, and manage storage objects directly against your project. The data work that used to mean hand-writing SQL in the dashboard happens in the conversation, with each write scoped and confirmed before it touches your tables.

  • Insert or update rows in a table from natural-language instructions
  • Run a parameterized read query and summarize the results
  • Apply a schema migration to add a column or index after you approve it
  • Upsert records and reconcile duplicates across a table
  • Manage storage bucket objects, uploading or removing files
  • Draft and run a backfill, then report the affected row count

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Supabase access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Supabase API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Supabase changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Supabase connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Supabase connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Supabase account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Supabase's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Supabase?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Supabase account it signs in with. Revoking access is one click in Supabase.

More on the Supabase connector

Supabase connector for claude.aiAirtable + Claude CodePostgreSQL + Claude CodeMySQL + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us