Supabase MCP Server

What is Supabase MCP Server?

Supabase MCP is the official Model Context Protocol server from Supabase that connects AI assistants like Cursor, Claude and Windsurf to your Supabase projects, so they can manage tables, run SQL and migrations, fetch config, read logs and deploy Edge Functions.

It is a hosted server at https://mcp.supabase.com/mcp that signs you in with OAuth, so most setups need no install and no access token. The code lives in the supabase-community/supabase-mcp repository under Apache-2.0. Local Supabase CLI and self-hosted Supabase also expose an MCP endpoint, with a smaller tool set and no OAuth.

How to use Supabase MCP Server?

Before you start: read Supabase's security guidance. Connecting an LLM to a database carries real risks, so prefer a development project, keep manual approval of tool calls on and consider read-only mode.

Server URL: https://mcp.supabase.com/mcp. During setup your client opens a browser to log in to Supabase; choose the organization that contains the project you want. You can also generate a project-specific URL from the MCP tab of the Connect dialog in the Supabase dashboard.

URL options (query parameters):

• project_ref=<id> scopes the server to one project and disables account-level tools
• read_only=true runs all queries as a read-only Postgres user
• features=database,docs enables only the listed tool groups

Claude Code

claude mcp add --scope project --transport http supabase "https://mcp.supabase.com/mcp"

Then run claude /mcp in a regular terminal (not the IDE extension), select supabase and choose Authenticate.

Cursor

Add to .cursor/mcp.json (or ~/.cursor/mcp.json for all projects):

{
  "mcpServers": {
    "supabase": {
      "url": "https://mcp.supabase.com/mcp"
    }
  }
}

VS Code

Add to .vscode/mcp.json:

{
  "servers": {
    "supabase": {
      "type": "http",
      "url": "https://mcp.supabase.com/mcp"
    }
  }
}

Codex

codex mcp add supabase --url "https://mcp.supabase.com/mcp"
codex mcp login supabase

Verify with /mcp inside Codex.

Other clients

In Claude.ai, Supabase is available as a connector in the directory. For any other client, copy the generic config into its format:

{
  "mcpServers": {
    "supabase": {
      "type": "http",
      "url": "https://mcp.supabase.com/mcp"
    }
  }
}

For CI or clients without a browser flow, create a scoped personal access token and send it as an Authorization: Bearer header. With the Supabase CLI running locally, the server is at http://localhost:54321/mcp.

Key features of Supabase MCP Server

• Official, hosted server with OAuth 2.1 sign-in: no local install or token for most clients
• Tools for projects, database, Edge Functions, logs, advisors, branching, storage and docs
• read_only=true mode that executes SQL as a read-only Postgres user
• Project scoping with project_ref to keep the agent inside one project
• Feature groups to expose only the tools a task needs
• Cost confirmation before creating projects or branches
• Works with the local Supabase CLI and self-hosted Supabase (limited tools)
• @supabase/mcp-server-supabase package for typed tool schemas in the Vercel AI SDK

Supabase MCP Server tools

The page lists 29 tools, organized into feature groups. All groups except Storage are enabled by default.

• Account: list_organizations, list_projects, create_project, pause_project and restore_project. get_cost and confirm_cost make the agent state and confirm costs before creating a project or branch.
• Database: list_tables, list_extensions, list_migrations, apply_migration for DDL and execute_sql for queries.
• Debugging: query_logs and get_advisors surface logs and security or performance advisories.
• Development: get_project_url, get_publishable_keys and generate_typescript_types.
• Edge Functions: list_edge_functions, get_edge_function and deploy_edge_function.
• Branching (experimental, paid plan): create_branch, merge_branch, reset_branch, rebase_branch and delete_branch.
• Docs: search_docs queries the Supabase documentation.

Use cases of Supabase MCP Server

• Schema work: "Create a profiles table linked to auth.users with row level security, as a migration."
• Data questions: "How many users signed up last week? Use read-only SQL."
• Debugging: "Check the API logs for errors in the last hour and run the security advisor."
• Front-end typing: "Generate TypeScript types for my database and update types.ts."
• Edge Functions: "Deploy a function that sends a welcome email on signup."
• Safe experimentation: "Create a development branch, apply this migration there, and show me the diff."

Supabase MCP Server vs alternatives

The Supabase MCP server knows about Supabase-specific features such as projects, Edge Functions, advisors and branching. If you only need SQL access to a Postgres database, including a Supabase database via its connection string, a general server like Postgres MCP works but cannot manage the platform. Older community projects named "supabase-mcp" exist on GitHub; the official hosted server is the maintained option.

Troubleshooting Supabase MCP Server

• Wrong or missing projects: during OAuth you picked an organization that doesn't contain the project. Re-authenticate and choose the right organization, or scope the URL with project_ref.
• Claude Code doesn't authenticate: run claude /mcp in a regular terminal, not the IDE extension, then select supabase and Authenticate.
• Mutating tools are missing: the URL has read_only=true, which disables them. Remove it only on a non-production project.
• Fewer tools than expected: the local CLI and self-hosted environments offer a limited subset with no OAuth, and Storage is off by default. Add groups with features=.
• No browser in CI: use a scoped personal access token in an Authorization: Bearer header instead of OAuth.