Supabase MCP 🔌 MCP server Freemium

What it does

Supabase MCP is Supabase's official server for connecting AI agents to your Supabase projects. It lets an agent handle the backend work you would otherwise do in the dashboard: list tables, write and apply migrations, run SQL, read logs, check security and performance advisors, generate TypeScript types and deploy Edge Functions. For vibe coders building on Supabase, the agent can shape the database and debug it in the same session where it writes the app code. The server is Apache-2.0 licensed. A hosted version runs at mcp.supabase.com, and the Supabase CLI and self-hosted Supabase also include a local endpoint with fewer tools.

Tools it gives your agent

Tools come in feature groups you can switch on or off:

• Database: list_tables, list_migrations, apply_migration, execute_sql
• Debugging: query_logs, get_advisors
• Development: project URL, publishable keys, generate_typescript_types
• Edge Functions: list, read and deploy functions
• Account: list, create, pause and restore projects, with cost checks
• Docs: search_docs
• Branching (experimental, paid plans) and Storage (off by default)

Works with

It works with any MCP client that supports remote HTTP servers, including Claude Code, Cursor, Windsurf, Codex, Copilot and Gemini CLI. If your client is not in Supabase's setup docs, you can copy the plain URL config into it. The server asks you to sign in with Supabase the first time you use it. For the local Supabase CLI, connect to http://localhost:54321/mcp.

How to connect

claude mcp add --scope project --transport http supabase "https://mcp.supabase.com/mcp"

To scope it to one project with read-only access, add ?project_ref=<id>&read_only=true to the URL.

Cost and limits

The MCP server is free. What you can do with it depends on your Supabase plan: branching tools, for example, need a paid plan. Check Supabase's pricing page for current plan limits.

Safety notes

Supabase itself warns about the risks of connecting an agent to a database. The agent works with your developer permissions, and malicious rows can carry prompt injection that tricks it into running harmful SQL. Use read_only=true, which runs queries as a read-only Postgres user. Scope the server to one project with project_ref, and switch on only the feature groups you need. Point it at a development project or branch rather than production. Keep manual approval of tool calls turned on in your client.