What it is
The Supabase MCP Server connects agents to your Supabase projects through https://mcp.supabase.com/mcp, with OAuth sign-in and dynamic client registration, so no token is needed for interactive use. The docs list 33 tools in eight feature groups: database (execute_sql, apply_migration, list_tables), debugging (query_logs, get_advisors), development, Edge Functions, account management, docs, branching and storage. All groups except storage are on by default.
URL parameters scope the server: project_ref limits it to one project and drops account tools, read_only=true runs SQL as a read-only Postgres user, and features picks tool groups. For CI, a scoped personal access token can be limited to one project and named permissions. Local Supabase CLI (localhost:54321/mcp) and self-hosted setups get a smaller tool set and no OAuth.
Version 0.14.0 of the open-source server shipped on 14 October 2026. In clients that support MCP elicitation, the server asks for confirmation before destructive SQL and before creating paid projects or branches.
Install
https://mcp.supabase.com/mcpOur review
Supabase's server lets an agent do most of a backend developer's day. It can design a schema, apply a migration, generate TypeScript types, deploy an Edge Function, query the logs with SQL and then run the security and performance advisors. The docs' configuration panel writes the URL for each client, and the dashboard can generate one per project.
The guardrails are better than most. In clients that support MCP form elicitation, execute_sql and apply_migration ask before SQL the server classifies as destructive, and create_project and create_branch show the price and billing interval before anything is created. Edge Function secrets are typed into the Supabase dashboard, never into chat. Supabase is careful to call all of this a guardrail rather than a guarantee: a skip_elicitations URL parameter turns the prompts off, and some clients answer elicitations automatically.
The defaults are permissive. The plain URL enables every group except storage with write access across every project in the organisation you pick. Supabase's own prompt-injection example, a support ticket that tells the agent to select from a sensitive table, is exactly what happens when a developer reads customer data through a write-enabled agent. SQL results are wrapped in instructions telling the model to ignore commands in the data, which the docs admit is not foolproof. Scoped access tokens now narrow CI use to one project and named permissions, but OAuth apps still have to be granted every scope.
At volume, the Management API's limit of 120 requests a minute per user, per project, per endpoint is the ceiling an agent meets. Local CLI and self-hosted users get fewer tools. Neon's server is the closer rival for plain Postgres with branching, while Supabase's covers the functions, logs and advisors around the database too.
Where it earns its place
A solo developer building a SaaS on Supabase Pro
Add a table, migration and Edge Function for a new feature in one session
Connects with project_ref set to the development project; the agent calls apply_migration, generate_typescript_types and deploy_edge_function, then get_advisors to catch missing row-level security. Pro is $25 a month, which includes $10 of compute.
A platform engineer at a 20-person startup
Run a nightly agent in CI that checks production for slow queries and security warnings
Uses a scoped access token limited to one project's read permissions, with read_only=true and features=debugging. Supabase advises unattended routines stay read-only and report rather than fix, so the agent opens a ticket instead of changing anything.
A tech lead on Supabase Team testing risky schema changes
Try a migration on a throwaway copy before it touches production
The agent calls create_branch, which pauses to show the $0.01344-an-hour branch rate for approval, applies the migration there, and merges only after review. Branching needs a paid plan.
Before you commit
- Setup
- Add https://mcp.supabase.com/mcp to Claude Code, Codex, Cursor, Gemini CLI, ChatGPT or another client and sign in with OAuth, choosing the organisation; a first list_tables call takes a few minutes.
- Integrations
- 33 tools, 30 on by default: execute_sql, apply_migration, list_tables, query_logs, get_advisors, generate_typescript_types, deploy_edge_function, create_branch, merge_branch, search_docs and storage tools (off by default).
- Data and privacy
- Hosted by Supabase and acting with your developer permissions; table contents returned to the model can carry prompt injection. Supabase says not to give the server to customers. The Team plan ($599 a month) adds SOC 2 and ISO 27001.
- Cost at scale
- No server fee. Pro is $25 a month plus $10 for each extra project; branches cost $0.01344 an hour each; the Management API allows 120 requests a minute per user, project and endpoint.
- Limits
- Confirmations need a client with MCP elicitation; OAuth app scopes are all-or-nothing; branching is experimental and paid-only; local CLI and self-hosted get a limited tool set.
What's good
- 33 tools across schema, SQL, migrations, functions, logs and advisors
- Project scoping, read-only Postgres role and feature groups
- Confirmation prompts for destructive SQL and paid resources
- Scoped personal access tokens for CI
What's not
- Write access to every project in the org unless you scope it
- OAuth apps still require every scope
- Prompts depend on client elicitation support and can be skipped
- Smaller tool set and no OAuth for local and self-hosted
Best for
Developers building on hosted Supabase who want an agent to manage schema, functions and debugging, ideally on development branches.
Alternatives
Supabase MCP Server: common questions
- Is Supabase MCP Server worth it?
- Supabase's server reaches well past the database into functions, logs and branches, and every safe setting it needs exists, though none of them is the default. We rate it 4.6 out of 5.
- How much does Supabase MCP Server cost?
- Server is free. Supabase Free allows 2 active projects, paused after a week idle; Pro from $25/month with $10 compute credit; Team $599. Branches $0.01344/hour.
- What are the downsides of Supabase MCP Server?
- Write access to every project in the org unless you scope it; oAuth apps still require every scope; prompts depend on client elicitation support and can be skipped; smaller tool set and no OAuth for local and self-hosted.
- Who is Supabase MCP Server best for?
- Developers building on hosted Supabase who want an agent to manage schema, functions and debugging, ideally on development branches.
- How much does Supabase MCP Server cost for a team or in production?
- No server fee. Pro is $25 a month plus $10 for each extra project; branches cost $0.01344 an hour each; the Management API allows 120 requests a minute per user, project and endpoint.
- Is Supabase MCP Server safe for company data?
- Hosted by Supabase and acting with your developer permissions; table contents returned to the model can carry prompt injection. Supabase says not to give the server to customers. The Team plan ($599 a month) adds SOC 2 and ISO 27001.
- What are the best Supabase MCP Server alternatives?
- The closest alternatives we have reviewed are Neon MCP Server, MongoDB MCP Server and MCP Toolbox for Databases.
Answers checked Oct 22, 2026.
Make Supabase MCP Server? Show this rating on your site
