Enables LLMs to query Supabase databases and understand their structure through a Model Context Protocol.
Connect Supabase to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Enables LLMs to query Supabase databases and understand their structure through a Model Context Protocol. The supabase mcp server is what makes that connection.
A Model Context Protocol (MCP) server for interacting with Supabase databases. This server provides tools for querying tables and generating TypeScript types through the MCP interface.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
query_table — Query a specific table with schema selection and where clause supportgenerate_types — Generate TypeScript types for your Supabase database schemaConfiguration is passed through the environment: SUPABASE_URL, SUPABASE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
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 — query_table, generate_types — is a fair guide to whether it matches your workflow. It is maintained by NightTrek; 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 |
|---|---|
| query_table | Query a specific table with schema selection and where clause support. |
| generate_types | Generate TypeScript types for your Supabase database schema. |
{
"mcpServers": {
"supabase": {
"command": "node",
"args": ["/absolute/path/to/supabase-mcp-server/build/index.js"],
"env": {
"SUPABASE_URL": "your_project_url",
"SUPABASE_KEY": "your_service_role_key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SUPABASE_URL | Endpoint or connection string the server talks to. | Yes |
| SUPABASE_KEY | Credential the server authenticates with. | Yes |
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.