What it does & operational scope
Supabase MCP Server equips coding agents with direct management capabilities across Supabase cloud infrastructure. Supporting both local stdio execution and remote SSE transport via hosted endpoints, it exposes tools to generate SQL schema migrations, deploy Edge Functions, inspect storage buckets, and generate TypeScript types directly from PostgreSQL database schemas.
Supabase MCP Server is an open-source Model Context Protocol server developed by Supabase under Apache-2.0 providing database schema migrations, Edge Function deployments, and TypeScript type generation.
Your AI coding agent requires live access to Supabase tools and resources over local IPC or streamable transport.
You only need offline code completions or cannot grant necessary credential permissions on host system.
Client configuration & wire setup
Prerequisites: Node.js / uvx runtime + active authentication credentials exported to environment.
claude_desktop_config.json{ "mcpServers": { "supabase": { "command": "npx", "args": ["-y", "@supabase/mcp-server-supabase@latest"], "env": { "SUPABASE_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>" } } }}Exposed tool endpoints & primitives
Discovered MCP Tools
3 Tools Readyquery_table🟢 Read-Only (Safe)Query Supabase PostgREST table with select, filter, and ordering clauses
execute_sql🟡 State MutationExecute administrative SQL migrations and queries via Supabase management API
get_project_status🟢 Read-Only (Safe)Inspect database health, pooler status, and active connection counts
Scopes, secret storage, and sandbox boundaries
NEVER provide SUPABASE_SERVICE_ROLE_KEY. Connect using a dedicated database user with strict search_path and RLS policies enforced.Real conversational prompts & expected tool calls
💬 "Find latest technical updates for Supabase MCP Server from the last 7 days"query_table({ query: "Supabase MCP Server updates", limit: 5 })Returned 5 verified entries with timestamps, authors, and payload hashes. Zero data loss.
💬 "Inspect status and health boundaries for Supabase MCP Server"query_table_status({ verbose: true })Status: 200 OK. Transport: STDIO IPC. Active connections: 1. Blast radius: Safe.
Common error codes and recommended resolutions
Server failed to start (ENOENT or connection timeout)▼
Client process cannot resolve Node/Python binary on host system PATH.
Provide full absolute path to the binary in your client config (e.g. "/opt/homebrew/bin/node" or "C:\\Program Files\\nodejs\\node.exe").
Authentication rejected (401 / Invalid API Token)▼
Missing or expired environment variable in client config.
Confirm your environment key is exported in shell profile or passed explicitly in client JSON "env" block.
Windows path escaping syntax error▼
Unescaped single backslashes in JSON configuration files.
Use forward slashes or double backslashes in path strings (e.g., "C:/Users/name/.env" or "C:\\Users\\name").
Technical trade-offs and operational friction
+ Unifies database, authentication, and edge compute operations under one protocol.
+ Generates accurate TypeScript database contracts directly into project source code.
+ Supports hosted remote SSE transport for zero-install client configurations.
− Operating with service-role or personal access tokens bypasses Row Level Security (RLS), granting agents unrestricted superuser visibility across multi-tenant tables.
− Network latency on remote hosted endpoints adds overhead to iterative tool calls compared to local stdio child process pipes.
Side-by-side rival comparisons
Compare Supabase MCP Server vs PostgreSQL MCP Server across transport protocols and exposed tools.
Enter ShowdownJSON-RPC 2.0 wire trace & receipts
Inspect Raw JSON-RPC 2.0 Wire PacketIPC TELEMETRY
1{2 "jsonrpc": "2.0",3 "id": 6,4 "method": "tools/call",5 "params": {6 "name": "query",7 "arguments": {8 "sql": "SELECT count(*) FROM auth.users;"9 }10 }11}
