Transform your AI conversations from lost chat history into a searchable, organized knowledge base. This system captures insights from both ChatGPT
Chatgpt Supabase Api MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Transform your AI conversations from lost chat history into a searchable, organized knowledge base. This system captures insights from both ChatGPT Enterprise and Claude Desktop, storing everything in a structured database for long-term.
Once Chatgpt Supabase Api is connected, these are the calls the assistant has available:
SUPABASE_URL — SUPABASE_ANON_KEYPrerequisites — The Prerequisites tool exposed by this serverComponents — The Components tool exposed by this serverCategories — The Categories tool exposed by this serverBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 4 environment variables: SUPABASE_ACCESS_TOKEN, SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_PROJECT_REF. 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.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Chatgpt Supabase Api's toolset — SUPABASE_URL, Prerequisites, Components and 1 more — is a fair guide to whether it matches your workflow. It is maintained by kellyoconor; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| SUPABASE_URL | SUPABASE_ANON_KEY |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Components | The Components tool exposed by this server. |
| Categories | The Categories tool exposed by this server. |
{
"mcpServers": {
"supabase": {
"command": "node",
"args": ["/path/to/supabase-mcp/packages/mcp-server-supabase/dist/transports/stdio.js"],
"env": {
"SUPABASE_ACCESS_TOKEN": "your_token",
"SUPABASE_URL": "your_url",
"SUPABASE_ANON_KEY": "your_key",
"SUPABASE_PROJECT_REF": "your_project"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SUPABASE_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| SUPABASE_URL | Endpoint or connection string the server talks to. | Yes |
| SUPABASE_ANON_KEY | Credential the server authenticates with. | Yes |
| SUPABASE_PROJECT_REF | Configuration value read at startup. | 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.