Supabase MCP 远程 MCP 服务器 – 官方端点、工具列表与一键连接指南

🛡️ Official✓ VerifiedStreamable HTTPOAuth 2.1🛡️ A+~992 tok30 tools·Online34ms·30 天在线率: 100%·上次拨测 2 分钟前

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

本页收录其官方远程端点、传输协议、认证方式、全部工具 Schema、实时可用性拨测与安全审计结果,并为 Cursor、Claude Code、VS Code、ChatGPT 等 10 大客户端提供一键接入指引。

https://mcp.supabase.com/mcp
提供方
Supabase ↗
分类
🗄️ 数据库与后端即服务
Streamable HTTPhttps://mcp.supabase.com/mcp
Install in Cursor →

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

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

🧰 Supabase MCP 工具与 Schema(30)

ToolSafetyDescriptionParameters
list_organizations
~31 tok
🟢 ReadList Supabase organizations.—
get_organization
~33 tok
🟢 ReadGet details of a Supabase organization.—
list_projects
~28 tok
🟢 ReadList Supabase projects.—
get_project
~31 tok
🟢 ReadGet details of a Supabase project.—
get_project_url
~33 tok
🟢 ReadGet the API URL of a Supabase project.—
get_publishable_keys
~35 tok
🟢 ReadGet publishable/anon API keys for a project.—
get_cost
~33 tok
🟢 ReadEstimate the cost of a new project or branch.—
confirm_cost
~35 tok
🟢 ReadConfirm a cost estimate before resource creation.—
create_project
~30 tok
🟠 WriteCreate a new Supabase project.—
pause_project
~29 tok
🟠 WritePause a Supabase project.—
restore_project
~32 tok
🟠 WriteRestore a paused Supabase project.—
list_tables
~31 tok
🟢 ReadList tables in a project database.—
list_extensions
~32 tok
🟢 ReadList installed Postgres extensions.—
list_migrations
~31 tok
🟢 ReadList applied database migrations.—
apply_migration
~35 tok
🟠 WriteApply a SQL migration to the project database.—
execute_sql
~35 tok
🔴 DestructiveExecute arbitrary SQL against the project database.—
get_logs
~32 tok
🟢 ReadRetrieve recent logs for a Supabase service.—
get_advisors
~34 tok
🟢 ReadGet security and performance advisor findings.—
generate_typescript_types
~38 tok
🟢 ReadGenerate TypeScript types from the database schema.—
search_docs
~31 tok
🟢 ReadSearch the Supabase documentation.—
create_branch
~33 tok
🟠 WriteCreate a development branch of a project.—
list_branches
~32 tok
🟢 ReadList development branches of a project.—
delete_branch
~30 tok
🔴 DestructiveDelete a development branch.—
merge_branch
~33 tok
🔴 DestructiveMerge a development branch into production.—
reset_branch
~33 tok
🔴 DestructiveReset a development branch to a prior state.—
rebase_branch
~34 tok
🟠 WriteRebase a development branch onto production.—
deploy_edge_function
~34 tok
🟠 WriteDeploy an edge function to a project.—
list_edge_functions
~31 tok
🟢 ReadList deployed edge functions.—
get_edge_function
~32 tok
🟢 ReadGet details of an edge function.—
create_storage_bucket
~31 tok
🟠 WriteCreate a storage bucket.—

🛡️ 安全评级、质量与上下文 Token 审计

🛡️ 安全评级 A+上下文 Token 开销: ~992 tokens(该服务端 30 个工具定义注入每次系统提示词)

估算单次调用 Token 成本 →

  • No prompt-injection or hidden-character anomalies detected in tool descriptions
  • Streamable HTTP primary endpoint (current 2025-03-26 transport)
  • OAuth 2.1 with PKCE S256 enforced
  • Official first-party endpoint operated by the vendor
  • Manually verified by RemoteMCP.net

🔐 OAuth 2.1 与安全

认证方式
OAuth 2.1
动态客户端注册(DCR)
✅ 支持
PKCE S256
✅ 支持
Scopes
all
受保护资源元数据
https://mcp.supabase.com/.well-known/oauth-protected-resource
审计 OAuth 2.1 配置 →

📡 官方远程端点与传输协议

远程端点 https://mcp.supabase.com/mcp 采用 Streamable HTTP(流式 HTTP,2025-03-26 规范)。Streamable HTTP 在单一 POST 端点上完成 JSON-RPC 双向交互,是当前 MCP 规范推荐的传输方式,可直接被 Claude、Cursor、VS Code 等客户端以 URL 形式接入,无需 npx mcp-remote 桥接。

接入前可将端点粘贴至本站 在线 MCP Inspector 实测 initialize / tools/list 握手,确认真实协议行为。

🔐 认证与权限机制

认证方式为 OAuth 2.1。首次连接时客户端会收到 401 挑战并从 WWW-Authenticate 头解析 RFC 9728 受保护资源元数据,随后自动完成授权服务器发现(RFC 8414)、动态客户端注册(DCR)与 PKCE S256 浏览器授权流程——你只需在浏览器中点击一次授权,无需手工粘贴任何密钥。

🛡️ 上下文开销与安全审计

该服务端当前登记 30 个工具,全部定义合计约 992 tokens,会在每次请求时注入模型系统提示词。安全评级为 A+,官方直营来源。工具名与 Schema 越精简,对上下文窗口的"税"越低;可用 feecalculator.app 估算每次调用的边际成本。

🧩 主流客户端快速接入

本站为 Supabase MCP 生成了 Cursor / Claude Code / VS Code / ChatGPT / Windsurf / Kiro / Codex / Cline / Gemini 等 10 大客户端的专属配置——包括一键 deeplink、claude mcp add 命令与 JSON/TOML 片段。下方选择你的客户端即可查看 1 分钟接入步骤。代表性工具包括 list_organizations、get_organization、list_projects、get_project、get_project_url 等。

📖 Supabase 详解

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.

Official Supabase MCP Endpoint & Transport Architecture

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

Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Supabase MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.

Authentication, Scopes & Permission Boundaries

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.

Of the 5 cataloged tools, 3 are read-only and 2 can write or mutate state (create resources, run SQL, post messages). Grant access only to the accounts and projects you intend agents to act on, and prefer scoped credentials or a dedicated workspace where the provider supports them.

Common Troubleshooting & Connection Tips

  • 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.

🚀 如何接入 Supabase MCP 远程 MCP

  1. 获取远程端点 — 复制官方端点 https://mcp.supabase.com/mcp。
  2. 写入客户端配置 — 在 Cursor 的 mcp.json / Claude Code CLI / 其他客户端中添加该 URL(见下方分客户端指南)。
  3. 授权并验证 — 完成浏览器 OAuth 授权后,在本站 Inspector 中运行 initialize 与 tools/list 验证连通性。

🔌 Supabase × 各客户端连接指南

❓ 常见问题

Supabase MCP 远程 MCP 服务器是官方提供的吗?

本条目标记为「官方直营」。端点由 Supabase 官方运营,所有收录端点均经过真实 MCP initialize 握手验证。

如何在 Claude / Cursor 中连接 Supabase MCP?

复制远程端点 https://mcp.supabase.com/mcp:Claude Code 执行 claude mcp add --transport http supabase https://mcp.supabase.com/mcp;Cursor 可直接使用本页的一键 deeplink 或在 ~/.cursor/mcp.json 中添加 { "mcpServers": { "supabase": { "url": "https://mcp.supabase.com/mcp" } } }。首次调用会自动弹出 OAuth 2.1 授权页面。

连接时返回 401 或需要密钥怎么办?

401 是 OAuth 2.1 的正常挑战响应——客户端会依据 RFC 9728 元数据自动完成授权,无需手工处理。若授权流程中断,可用本站 OAuth 2.1 Debugger 定位 PRM / DCR / CORS 配置问题。

本地 stdio MCP 和这个远程 MCP 有什么区别?

本地 MCP 通过 npx/uvx 在你的机器上启动 stdio 子进程,依赖本地运行时且密钥以明文写入配置文件;远程 MCP 是 Supabase 托管的 HTTPS 端点,免安装、支持 OAuth 2.1 授权流,且同一端点可跨桌面与移动端复用。详见 本地 vs 远程 MCP 对比。

🔗 同类远程 MCP 服务端