Claude Supabase connectorWhat Claude can do in your Supabase account.
The Claude Supabase connector exposes 32 tools. 18 read your organisations, projects, tables and settings, 12 change something, including raw SQL, and 2 are listed without a description. Below: what Claude reaches, what it can break, and the safeguards Supabase asks for.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when your database answers in plain words
Supabase describes its connector as a way for an assistant to query and work on your projects on your behalf. In practice, you ask Claude which tables exist, what a migration changed or why a function fails, and it goes to look instead of you opening the dashboard. The same access that makes this handy is why Supabase spends so much of its page on risk: this connector can change a live database.
Understand a project fast. A product manager inherits an app and asks what is in the database. Claude lists the tables with list_tables, the installed extensions with list_extensions and the migration history with list_migrations.
Catch problems early. get_advisors returns Supabase's security and performance advisors, so Claude can flag a weak spot before it reaches users.
Ship a change. A developer asks for a new column: apply_migration applies the migration, and deploy_edge_function pushes an updated Edge Function. execute_sql runs any SQL query, reads and writes alike unless read-only mode is on.
What it will not do on its own: stay safe by default. Supabase recommends scoping to one project, turning on read-only mode and limiting tool groups before touching production. Nothing runs by itself either: no tool reacts to a new row. For that, a scenario tool fits better, and the Supabase n8n integration and Supabase Make integration pages cover it. They do different jobs.
The vocabulary in one minute
Five words you will meet while plugging Supabase into Claude.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector opens to Claude. Claude picks the ones it needs by itself; the directory lists them by name.
- Authorization
- The sign-in screen of Supabase itself, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it finishes something that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Supabase.
Connect Supabase to Claude in three steps
- 01
Find Supabase in Claude
In Claude's settings, open Customize, then Connectors, and look for Supabase in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row and sign in to Supabase in the window the service opens itself. If the link breaks one day, use Disconnect, then plug it back in from the same row.
- 03
Read the authorization screen
Read the service's screen before you accept. It belongs to Supabase, not Claude, and it decides what the access covers. You can also withdraw that access later from your Supabase account.
The 32 tools, grouped by what they do
Supabase gives Claude 32 tools: 18 that read your account, 12 that change something in it, and 2 no official source describes.
Three groups: what Claude reads, what it changes, and two names no source explains. Names stay in English, as Claude shows them.
- 18 read
- 12 write
- 2 not documented
What Claude reads (18)
18 toolsEighteen tools that look at organisations, projects, the database, functions and storage settings without changing them.
list_organizations
Lists the Supabase organisations your account belongs to. Supabase files it under organisation management, next to the tool that opens one organisation in detail.
get_organization
Returns the details of one organisation. Supabase files it under organisation management, alongside the listing tool.
list_projects
Lists your Supabase projects so Claude knows which one you mean. Supabase pairs it with the tool that returns one project's details.
get_project
Shows one project in full, the companion of the listing tool. Supabase groups the two under a single line, so Claude uses this one once it knows which project you mean.
get_cost
Gives cost information; Supabase's list says no more than that, and pairs it with confirm_cost.
list_branches
Lists the development branches of a project. Supabase puts it in its branch management group.
list_tables
Lists every table in the database, a quick picture of what the project stores.
list_extensions
Shows which Postgres extensions are available and which are installed on the database.
list_migrations
Returns the list of database migrations, the record of every structural step taken so far.
get_advisors
Returns Supabase's security and performance advisors for the project, the warnings it raises about its own setup.
get_project_url
Gives the API address of a project, the one an app uses to reach it.
get_publishable_keys
Returns a project's publishable API keys, plus the legacy anon keys.
generate_typescript_types
Generates TypeScript types from your database schema, so application code matches the tables exactly. The database itself stays as it is.
search_docs
Searches Supabase's documentation, so Claude answers how-to questions from the source rather than from memory.
list_storage_buckets
Lists a project's storage buckets. It belongs to the Storage group, which Supabase leaves off by default.
get_storage_config
Reads the storage configuration of a project. Like the rest of the Storage group, it is disabled until you turn that group on.
list_edge_functions
Lists all the Edge Functions of a project, the server-side functions it hosts.
get_edge_function
Fetches one specific Edge Function of the project, picked out of the list.
What Claude changes (12)
12 toolsTwelve tools that create, alter or remove something, raw SQL included. No source describes a confirmation specific to them: the general rule below applies.
create_project
Approval: see the ruleCreates a new Supabase project. Supabase lists it with pausing and restoring under project management.
pause_project
Approval: see the rulePauses a project, one of the three project management actions Supabase lists.
restore_project
Approval: see the ruleRestores a project, the counterpart of pausing in Supabase's project management group.
create_branch
Approval: see the ruleCreates a development branch for the database. Supabase files it under branch management.
delete_branch
Approval: see the ruleDeletes a development branch, the removal tool of the branch management group.
merge_branch
Approval: see the ruleOne of three branch operations Supabase lists together, with no line of its own. It acts on a project's branches rather than reading them.
reset_branch
Approval: see the ruleAnother of the branch operations Supabase groups together without a separate description. It changes the state of a branch.
rebase_branch
Approval: see the ruleThe third branch operation in Supabase's list, again without its own description. It modifies a branch, it does not just read it.
apply_migration
Approval: see the ruleApplies a database migration, changing the structure of your tables for real.
execute_sql
Approval: see the ruleRuns SQL queries against the database. A query can read data or change it; Supabase offers a read-only mode that runs every query as a read-only Postgres user instead.
update_storage_config
Approval: see the ruleChanges the storage configuration of a project. It sits in the Storage group, off by default.
deploy_edge_function
Approval: see the ruleDeploys an Edge Function to the project, new or updated, so it starts running server-side.
Not documented (2)
2 toolsThe directory publishes these two names. Supabase's page does not describe them under these names, and this page will not guess.
confirm_cost
Supabase's page mentions this name next to get_cost under the heading of cost information, and says nothing more about it. No Claude page describes it either, so this page does not say whether it reads or changes anything.
get_logs
The directory lists this name, but Supabase's page describes a differently named logs tool and never this one. No source explains it, so this page leaves it undescribed.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.
On Team and Enterprise, workspace owners decide whether a member can let some actions through without being asked every time. They can also cap what a connector may do for the whole organisation, keeping reading open and closing writing, for example. That setting applies to everyone and nobody gets around it from their own account. And Claude works with your rights, nothing more: what you cannot reach in Supabase stays out of its reach too.
Which plans it works on
None of the 819 sheets in the official directory shows availability by plan. The answer, connector by connector, is not published anywhere: it is a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a row is inserted, a function fails or a migration lands.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The partner badge in the directory is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as described. Everything below comes from Supabase's documentation, since neither Claude's help centre nor Anthropic's docs have a page on this connector. For a connector with a gentler write surface, compare with the Claude airtable connector.
Need help connecting Supabase to Claude?
A person reads every message.
