Why you'd want it
Supabase hosts the server at mcp.supabase.com, so most clients need only the URL and an OAuth login to reach your projects. Tools are grouped into features (database, debugging, development, Edge Functions, account, docs, branching, storage) that you can restrict, and you can scope the server to one project or run it in read-only mode, where SQL runs as a read-only Postgres user. The npm package also exports tool schemas for the Vercel AI SDK MCP client and a handler for serving the tools from your own endpoint.
Best for
- Apps built on Supabase
- Letting a coding agent inspect schemas and apply migrations
- Debugging with project logs and advisors
Use it when
Your app runs on Supabase and you want the agent to read schemas, run SQL, apply migrations or check logs from your editor.
Skip it if
You do not use Supabase, or you cannot keep it away from production data: Supabase warns about prompt injection, recommends project scoping and read-only mode, and says not to give the server to your end users. The local CLI and self-hosted setups get only a subset of tools and no OAuth.
Editor's note
Moved from supabase-community/supabase-mcp to supabase/mcp.