MCP server for Supabase CRUD operations
Supabase MCP server exists for a simple reason — assistants are far more useful when they can act on Supabase directly instead of describing what you should do. MCP server for Supabase CRUD operations.
A Model Context Protocol (MCP) server that allows Claude and other LLMs to interact with Supabase to perform CRUD operations on Postgres tables.
The server ships on npm as supabase-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Once Supabase is connected, these are the calls the assistant has available:
Parameters — - table (string): Name of the table to queryYou will need 5 environment variables: SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, MCP_API_KEY, MCP_SERVER_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Supabase's toolset — Parameters — is a fair guide to whether it matches your workflow. It is maintained by cappahccino; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Supabase's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Parameters | - table (string): Name of the table to query |
{
"mcpServers": {
"supabase-2": {
"command": "npx",
"args": ["-y", "supabase-mcp"],
"env": {
"SUPABASE_URL": "your-value",
"SUPABASE_ANON_KEY": "your-value",
"SUPABASE_SERVICE_ROLE_KEY": "your-value",
"MCP_API_KEY": "your-value",
"MCP_SERVER_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SUPABASE_URL | Endpoint or connection string the server talks to. | Yes |
| SUPABASE_ANON_KEY | Credential the server authenticates with. | Yes |
| SUPABASE_SERVICE_ROLE_KEY | Credential the server authenticates with. | Yes |
| MCP_API_KEY | Credential the server authenticates with. | Yes |
| MCP_SERVER_HOST | Endpoint or connection string the server talks to. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.