Supabase MCP server
Supabase in any MCP client, through Memtro: Supabase does not publish this server. Memtro's Supabase connector reads Supabase through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Supabase account management: organisations and members, projects with region and status, service health, edge functions, database branches, migration history, and the security and performance advisors. Can pause, restore, restart and rename projects, create, merge, reset and delete branches, apply migrations, delete edge functions and create restore points. Never reads project API keys, secrets or table data.
Reads
supabase_list_organizationsSupabase organisations this token can see, with their slugs.supabase_list_projectsSupabase projects: ref, name, organisation, region, status (ACTIVE_HEALTHY, INACTIVE for paused, COMING_UP…), Postgres version and created date.supabase_list_membersMembers of a Supabase organisation: name, role and whether they have MFA on.supabase_project_healthHealth of a Supabase project's services (auth, db, pooler, realtime, rest, storage): status per service and any error.supabase_list_functionsEdge functions deployed in a Supabase project: slug, name, status, deployed version, whether JWT verification is on, and created and updated times.supabase_list_branchesDatabase branches of a Supabase project (preview and persistent branches): name, git branch and pull request, whether default or persistent…supabase_list_migrationsMigration history applied to a Supabase project's database: version and name, newest last as Supabase returns them.supabase_advisorsSupabase's security or performance advisor findings for a project: which check fired (RLS disabled, unindexed foreign key…), level (ERROR, WARN…
Acts, when you ask
These change something in Supabase. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
supabase_pause_projectPause a Supabase project.supabase_restore_projectRestore (unpause) a paused Supabase project.supabase_restart_projectRestart a Supabase project's services.supabase_rename_projectRename a Supabase project (the display name only; its ref and URLs do not change).supabase_create_branchCreate a database branch of a Supabase project, a separate Postgres instance billed per hour while it exists.supabase_merge_branchMerge a database branch's migrations into its parent (usually production) project, changing the live schema.supabase_reset_branchReset a database branch to a migration version (default its first), wiping the data and schema changes made on the branch since.supabase_delete_branchDelete a database branch and its data, immediately and permanently unless with_grace_period is true (a one-hour grace period…supabase_apply_migrationRun a SQL migration against a Supabase project's live database and record it in the migration history.supabase_delete_functionDelete an edge function from a Supabase project.supabase_create_restore_pointCreate a named restore point of a Supabase project's database (for example before a risky migration).
Connect it
First connect Supabase on Dashboard → Connections, then add Memtro to your client once. The Supabase tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Supabase connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Is our Supabase production project healthy right now?
- › Has the add_invoices_table migration been applied to production?
- › Which tables does the security advisor say have RLS disabled?
- › Which members of the Acme organisation have MFA turned off?
- › Create a restore point on production, then restart the project
Questions
- Is this an official Supabase MCP server?
- No. It is Memtro's MCP server with Memtro's Supabase connector behind it: the connector reads Supabase through its API with the credentials you connect on Dashboard → Connections, and Supabase publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Supabase?
- Only when you ask, and only what it has been granted: pause a project (its apps go offline); restore a paused project (resumes billed compute); restart a project's services (brief downtime); rename a project; create a database branch (billed hourly); merge a branch's migrations into its parent project; reset a branch to a migration version (branch data lost); delete a database branch (permanent); apply a SQL migration to a project's database; delete an edge function (permanent); create a named database restore point. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.