Supabase Official Remote MCP Server

🛡️ Official✓ VerifiedStreamable HTTPOAuth 2.15 tools·Online37ms·30d uptime: 100%·Last checked 18m ago

The hosted Supabase MCP (mcp.supabase.com/mcp) exposes your organization's projects to MCP clients: list projects, run SQL, apply migrations and fetch project config — protected by OAuth 2.1.

https://mcp.supabase.com/mcp

Provider: Supabase ↗
Source: https://github.com/supabase-community/supabase-mcp ↗
Categories: 🗄️ Databases & Backend-as-a-Service

中文简介

Supabase 托管 MCP 服务器。AI 代理可在 OAuth 授权范围内执行 SQL、应用迁移并生成 TypeScript 类型。

Streamable HTTPhttps://mcp.supabase.com/mcp

Install in Cursor →

Or add to ~/.cursor/mcp.json:

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

🔬 Test Live in Online Inspector 🔐 Audit OAuth 2.1 Config

🧰 Tools exposed by Supabase MCP (5)

Tool	Safety	Description	Parameters
list_projects	🟢 Read	List all Supabase projects in your organizations.	—
execute_sql	🟠 Write	Run arbitrary SQL against a Supabase project database. Can modify or delete data — review statements carefully.	project_id: stringquery: string
apply_migration	🟠 Write	Apply a database migration to a Supabase project. Potentially destructive — migrations can drop tables and columns.	project_id: stringname: stringquery*: string
get_project_url	🟢 Read	Get the API URL for a Supabase project.	project_id*: string
generate_typescript_types	🟢 Read	Generate TypeScript types from a project's database schema.	project_id*: string

🔐 OAuth 2.1 & Security

Auth type: OAuth 2.1
Dynamic Client Registration: ✅ Supported
PKCE S256: ✅ Supported
Scopes: all
Protected resource metadata: https://mcp.supabase.com/.well-known/oauth-protected-resource (expected location)

🔐 Audit OAuth 2.1 Config →

🧩 Recommended Agent Skills

📖 Guide

Supabase MCP — Remote MCP Server

The hosted Supabase MCP server authenticates against your Supabase account and can operate on any project you have access to — running SQL, applying migrations and generating types. That makes it powerful and dangerous in equal measure: Supabase recommends connecting agents to development or branching projects, not production, and the dashboard lets you restrict the server to read-only mode or a subset of projects.

Endpoint & Transport

Endpoint URL: https://mcp.supabase.com/mcp
Transport: Streamable HTTP

Authentication

Supabase MCP uses OAuth 2.1 — the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow — PKCE and Dynamic Client Registration, so no manual client setup is needed — and simply open a browser consent screen.

Available Tools (5)

Tool	Safety	Description
`list_projects`	read	List all Supabase projects in your organizations.
`execute_sql`	write	Run arbitrary SQL against a Supabase project database. Can modify or delete data — review statements carefully.
`apply_migration`	write	Apply a database migration to a Supabase project. Potentially destructive — migrations can drop tables and columns.
`get_project_url`	read	Get the API URL for a Supabase project.
`generate_typescript_types`	read	Generate TypeScript types from a project's database schema.

Connect in 30 Seconds

Claude Code — one command:

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

Cursor — add to ~/.cursor/mcp.json:

{ "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" } } }

Claude Desktop & stdio clients — bridge with mcp-remote:

{ "mcpServers": { "supabase": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.supabase.com/mcp"] } } }

On first connect your client opens a browser OAuth consent screen — approve it and tools become available immediately.

Troubleshooting

401 Unauthorized on connect — that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact WWW-Authenticate challenge.
"Session expired" / stale Mcp-Session-Id — just re-send initialize; stateless clients can ignore session headers entirely.
execute_sql and apply_migration can modify real data — enable read-only mode in the Supabase dashboard if you only need inspection.
OAuth grants are per-organization; you approve scopes during the consent screen.

🚀 How to Connect

Copy the Supabase MCP endpoint URL
The remote endpoint is https://mcp.supabase.com/mcp.
Add it to your MCP client
Claude Code: claude mcp add --transport http supabase https://mcp.supabase.com/mcp. Cursor: add "supabase": { "url": "https://mcp.supabase.com/mcp" } under mcpServers in ~/.cursor/mcp.json. Other clients work similarly.
Complete the OAuth consent
On first connection your client opens a Supabase consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
Verify with the online inspector
Paste https://mcp.supabase.com/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Supabase MCP's 5 tools respond.

❓ FAQ

What is the Supabase MCP remote MCP endpoint?

The primary endpoint is https://mcp.supabase.com/mcp. It is an official first-party server operated by Supabase, speaking the Streamable HTTP transport.

How do I authenticate with Supabase MCP?

Supabase MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.

I'm getting a 401 Unauthorized from Supabase MCP — what's wrong?

A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.

Which MCP clients work with Supabase MCP?

Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http supabase https://mcp.supabase.com/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, and Claude Desktop via the `mcp-remote` bridge.

What tools does Supabase MCP expose?

5 tools are cataloged in this directory — including `list_projects`, `execute_sql`, `apply_migration` and more. Use our online inspector to fetch the live tool list straight from the endpoint.

🔗 Connect Guides

Cursor

Connect Supabase MCP →

Claude

Connect Supabase MCP →

Claude Code

Connect Supabase MCP →

VS Code

Connect Supabase MCP →

ChatGPT

Connect Supabase MCP →

Windsurf

Connect Supabase MCP →

📛 Embed Status Badge in README

[![Remote MCP Status](https://remotemcp.net/api/badge/status/supabase.svg)](https://remotemcp.net/servers/supabase)

[![Test in Inspector](https://remotemcp.net/api/badge/inspect/supabase.svg)](https://remotemcp.net/inspector?url=https%3A%2F%2Fmcp.supabase.com%2Fmcp)

Related Servers

Neon MCPNeon

Neon's official remote MCP server for serverless Postgres. Agents can manage projects and branches and run SQL over the SSE transport with OAuth.

https://mcp.neon.tech/sse

🛡️ Official✓ VerifiedSSEOAuth 2.14 toolsDegraded166ms