Nobody has rated Supabase MCP yet. What it is like to build with is the part no download count can tell anyone.
Nobody has said anything about Supabase MCP yet.
The Supabase MCP server connects an AI coding agent to your Supabase account. Its tools are grouped by feature: Database (list tables, extensions and migrations, apply a migration, execute SQL), Debugging (query project logs, get security and performance advisors), Development (project URL, publishable keys, TypeScript types generated from the schema), Edge Functions, Account management, Docs search, Branching and Storage. Every group except Storage is on by default. It is a hosted server at https://mcp.supabase.com/mcp. For Claude Code the docs give: claude mcp add --scope project --transport http supabase "https://mcp.supabase.com/mcp". They also cover Codex, Gemini CLI, GitHub Copilot, Cursor, VS Code, Claude.ai, ChatGPT, Goose and others. The first connection opens a browser to sign in to Supabase, and no personal access token is needed. We think it is worth adding when your agent is building against a Supabase backend: it can read the real schema before writing a query, apply a migration, check the advisors afterwards, and regenerate types so the app code matches the database. The docs say plainly that connecting an LLM to your projects carries security risks, mainly prompt injection through content stored in your data, and recommend keeping manual approval on and reviewing each tool call. Two URL options narrow what it can reach: ?read_only=true runs every query as a read-only Postgres user, and ?project_ref=<id> scopes the server to one project.
The log is the half nobody can write on their own: an entry lands here the moment somebody names this tool in one. Attach it from the composer’s + menu.