← MCP

模型与开放条件Model & openness

它自己不调模型——被 MCP 客户端调用的接口实现。它把 Supabase 平台能力 （项目、数据库查询、迁移、日志、文档检索）包装成工具给编码 agent 用。

It calls no model itself — an interface implementation called by MCP clients. It wraps Supabase platform capabilities (projects, database queries, migrations, logs, docs retrieval) as tools for coding agents.

运行位置Where it runs

双形态：本地 npx 进程（stdio）+ 官方托管远程线；GitHub 2,983★， 最近推送 2026-10-29（GitHub API 核验）。

Two forms: local npx process (stdio) + an official hosted remote line; GitHub 2,983★, last push 2026-10-29 (GitHub API verified).

本地文件Local files

本地形态不直接读写你本机项目文件（那是 filesystem server 的活）—— 它操作的是 Supabase 云端项目：表、迁移、日志。

In the local form it does not directly read or write your local project files (that is the filesystem server's job) — it operates on Supabase cloud projects: tables, migrations, logs.

关机后的任务Tasks after shutdown

本地 stdio 随客户端生死；远程托管形态在 Supabase 侧。无后台任务语义。

Local stdio lives and dies with the client; the hosted remote form lives on Supabase's side. No background-task semantics.

工具与扩展Tools & extensions

数据库查询/迁移、项目管理、日志与诊断、docs 检索等； 工具可按需裁剪（官方支持选择性启用工具组）；完整清单以仓 README 为准。

Database queries/migrations, project management, logs and diagnostics, docs retrieval, etc.; tools can be trimmed on demand (the official side supports selectively enabling tool groups); the complete inventory follows the repo README.

上下文与记忆Context & memory

无 server 侧跨会话记忆——状态在 Supabase 项目本身（schema、数据）。

No server-side cross-session memory — state lives in the Supabase project itself (schema, data).

权限与限制Permissions & limits

凭据=Supabase 访问令牌，权限面大：能连项目级 API（含 SQL 执行面）。 官方提供工具裁剪与只读类工具区分，但 SQL 写/DDL 能力真实存在—— 接 agent 前按「给它一个能改库的凭据」这个最坏假设设防。

Credential = Supabase access token, a large permission surface: it can reach project-level APIs (including the SQL execution surface). The official side offers tool trimming and read-only tool distinctions, but SQL write/DDL capabilities genuinely exist — before hooking up an agent, defend on the worst-case assumption "you gave it a credential that can modify the database".

适合什么任务Best for

适合：编码 agent 直接管自家 Supabase 项目（查 schema、跑迁移、看日志）。 不适合：要「只读保险」的硬边界（裁剪能收窄但不是沙箱）；非 Supabase 栈项目。

Fits: coding agents directly managing your own Supabase projects (inspect schema, run migrations, read logs). Not a fit: hard boundaries needing "read-only insurance" (trimming narrows but is not a sandbox); non-Supabase-stack projects.

传输方式Transport

本地 stdio（npx 起进程）为主；官方另有托管远程端点线（细节以官方文档为准，未逐条核验）。 核验：仓 README 与 GitHub API（2026-10-21）。

Local stdio (npx starting a process) is primary; the official side also has a hosted remote endpoint line (details follow the official docs, not verified item by item). Verified: repo README and GitHub API (2026-10-21).

认证机制Authentication

Supabase 访问令牌（scope 可选配）；本地形态环境变量/参数传 token。 令牌轮换与最小权限实践官方文档有指引——未逐条核验细节。

Supabase access token (scopes configurable); the local form passes the token via env var/parameter. The official docs give guidance on token rotation and least-privilege practices — details not verified item by item.

权限范围Permission scope

项目级：读 schema、执行 SQL（含写/DDL）、管迁移、看日志。 工具组裁剪可缩小暴露面；无工具级人工审批机制的官方说明。

Project level: read schema, execute SQL (including writes/DDL), manage migrations, read logs. Tool-group trimming can shrink the exposure surface; no official docs for a tool-level human approval mechanism.

本页由This page is generated from the ai-handbook 数据层生成（CC BY 4.0）。data layer (CC BY 4.0). 方法论与坐标系定义见仓库内For the methodology and coordinate definitions, see METHODOLOGY.md.