Schema, queries, auth, and storage from Supabase — directly callable by LLMs
Maintained by Supabase, the Supabase MCP server exposes the full platform surface to LLM agents: SQL queries against your Postgres, Auth user management, Storage bucket operations, and Edge Function invocation. Combines the safety story of Postgres MCP with Supabase opinionated auth and storage. Best fit: teams already on Supabase who want their internal tooling to be agent-driven.
The whole platform is suddenly agent-callable. Auth + DB + Storage from one prompt.
Supabase MCP is the kind of all-in-one I want for our stack. The agent can provision a user, set their role, write the seed data, all in one conversation. Saves 20 minutes of admin per new customer onboarding.
RLS inheritance is the right default. Agent cannot read what the user cannot read.
Other MCP database servers give the agent service-role access by default. Supabase MCP respects the connecting user RLS. Agent is scoped, blast radius limited. This is the right model.
Great if you are on Supabase. Useless otherwise.
No criticism, just truth: this MCP is for Supabase customers. If you are on RDS or Neon, use Postgres MCP instead. We are on Supabase, so this is a clean win.
Methodology
Every review on this page is verified through GitHub OAuth and weighted by reviewer credibility, use-case match, and conflict-of-interest disclosure. Aggregate scores combine with recency decay so rankings reflect current reality. Read full methodology →
