Supabase is a Databases MCP server that lets Claude Code, Cursor, Windsurf and any MCP-compatible AI agent database, auth, storage via Supabase. Install in 1 minute with mcpizy install supabase-mcp.
Connect your Supabase account once — MCPizy stores the credentials encrypted and uses them whenever you run a recipe in managed mode.
mcpizy install supabase-mcpnpx -y supabase-mcplist_tablesList all tables in one or more schemas of the project
Inputs
schemasstring[]optionallist_extensionsList all Postgres extensions installed in the database
list_migrationsList all migrations applied to the project
apply_migrationApply a SQL migration (DDL). Use this for schema changes
Inputs
namestringrequiredquerystringrequiredexecute_sqlExecute raw SQL (DML/queries)
Inputs
querystringrequiredget_logsFetch logs for a service (api, postgres, auth, storage, realtime)
Inputs
servicestringrequiredget_advisorsGet security and performance advisors for the project
Inputs
typestringrequiredlist_edge_functionsList all Edge Functions in the project
deploy_edge_functionDeploy a new or updated Edge Function
Inputs
namestringrequiredfilesobject[]requiredgenerate_typescript_typesGenerate TypeScript types from the current schema
Works identically across clients. Only the config file path differs.
~/.claude.json{
"mcpServers": {
"supabase-mcp": {
"command": "npx",
"args": [
"-y",
"@supabase/mcp-server-supabase@latest",
"--access-token",
"${SUPABASE_ACCESS_TOKEN}"
],
"env": {
"SUPABASE_ACCESS_TOKEN": "sbp_..."
}
}
}
}.cursor/mcp.json{
"mcpServers": {
"supabase-mcp": {
"command": "npx",
"args": [
"-y",
"@supabase/mcp-server-supabase@latest",
"--access-token",
"${SUPABASE_ACCESS_TOKEN}"
],
"env": {
"SUPABASE_ACCESS_TOKEN": "sbp_..."
}
}
}
}~/.codeium/windsurf/mcp_config.json{
"mcpServers": {
"supabase-mcp": {
"command": "npx",
"args": [
"-y",
"@supabase/mcp-server-supabase@latest",
"--access-token",
"${SUPABASE_ACCESS_TOKEN}"
],
"env": {
"SUPABASE_ACCESS_TOKEN": "sbp_..."
}
}
}
}Paste any of these prompts into Claude Code, Cursor or another MCP-compatible client.
“List every table in the public schema and summarise the columns of `users`”
Uses: list_tables
“Create a new `invoices` table with columns id, user_id, amount, status — generate the migration”
Uses: apply_migration
“Run `SELECT COUNT(*) FROM auth.users` and show me the result”
Uses: execute_sql
“Deploy an Edge Function named `hello` that returns `Hello, world`”
Uses: deploy_edge_function
“Audit my database for security issues and generate fresh TypeScript types”
Uses: get_advisors, generate_typescript_types
Supabase MCP turns the Supabase dashboard into an agent-callable surface. Instead of clicking through the SQL editor or copying schemas into prompts, your AI runs `list_tables`, `apply_migration`, `execute_sql`, `deploy_edge_function` directly — same primitives, same auth model. The server uses a personal access token (not a project anon key), which means anything you can do as the project owner, the agent can do too. That power is the point and the risk.
We use Supabase MCP for three things daily. First, schema reconciliation: "look at my Postgres schema, compare to the Prisma model in `/db/schema.prisma`, and generate the migration." The agent reads both, drafts the SQL, and applies it after we approve. Second, on-call: "logs from the auth service in the last hour — anything 5xx?" The agent calls `get_logs` and `get_advisors` and surfaces the actual rows. Third, type generation: `generate_typescript_types` regenerates the `Database` type after every migration so the front-end stays in sync.
The honest comparison: Supabase MCP is far more capable than the bare Postgres MCP because it covers the whole platform (auth, storage, realtime, edge functions, advisors). If you're only using Postgres, the lower-surface postgres MCP is faster and has a smaller blast radius. If you're using Supabase end-to-end and want one tool that mirrors the dashboard, this is the right server. Token cost on schema operations is moderate (~1-3k tokens per table inspected); migration generation can spike to 5-10k on complex schemas.
The personal access token has full project rights — there is no read-only mode. Treat the MCP exactly like giving someone your Supabase dashboard password. For production, scope a separate project for the agent or run in a managed sandbox.
`apply_migration` and `execute_sql` are different code paths: migrations get versioned and tracked; raw SQL doesn't. If the agent runs DDL via `execute_sql`, the migration history will drift and `db diff` will misbehave. Tell the agent explicitly which to use.
Edge Function deploys via MCP skip the local CLI's import map resolution. If your function imports relative URLs or non-jsr deps, deploy will silently strip them. Test with `supabase functions serve` first, then deploy via MCP.
The advisor tool returns warnings as JSON — agents tend to flag every advisor item as critical. Ask for explicit severity filtering ("only show ERROR-level advisors") to avoid noise.
Honest pros/cons against the closest databases MCP servers.
| Server | Strengths | Trade-offs |
|---|---|---|
| Postgres MCP | Smaller blast radius, faster, works with any Postgres | No auth/storage/edge-functions — only DB |
| Neon MCP | Branching primitives (database branches), serverless Postgres | No auth/storage layers — pure DB platform |
| PlanetScale MCP | MySQL with branching, schema diff workflow | MySQL only, no row-level security primitive |
If Supabase doesn't fit your stack, these Databases MCP servers solve similar problems.
The Supabase MCP server is an Databases Model Context Protocol server that lets Claude Code, Cursor, Windsurf, VS Code with Copilot, and other MCP-compatible AI agents database, auth, storage via Supabase. It exposes Supabase's capabilities as tools the AI can call directly from your editor or CLI.
The fastest way is the MCPizy CLI: run `mcpizy install supabase-mcp` and MCPizy will add the server to your `.claude.json` automatically. You can also install it manually by adding an entry under `mcpServers` in `.claude.json` with the command `npx -y supabase-mcp` and restarting Claude Code.
Yes. The Supabase MCP server is free and open source (see the GitHub repository linked on this page). You may still need a Supabase account or API key to connect the server to the underlying service, but the MCP layer itself has no MCPizy subscription cost.
Yes. Any MCP-compatible client works — including Claude Code, Claude Desktop, Cursor (via `.cursor/mcp.json`), Windsurf, VS Code with Copilot Chat, and custom agents built on the MCP SDK. The same install command targets all of them; only the config file path differs.
Once installed, your AI agent can database, auth, storage via Supabase directly inside your conversation. Typical use cases include asking Claude Code or Cursor to run Supabase operations, inspect results, chain Supabase with other MCP servers (see our Workflow Recipes), and automate repetitive databases tasks without leaving your editor.