#1 Supabase MCP Server
Why it’s hereMost popular in this category on AllMCPs
Supabase MCP Server with support for SQL query execution and database exploration tools
The best MCP servers for Supabase — let AI agents query Postgres, manage tables and migrations, and work with Supabase projects from your editor.
Why it’s hereMost popular in this category on AllMCPs
Supabase MCP Server with support for SQL query execution and database exploration tools
Why it’s hereCommunity pick
MCP server for PostgreSQL: local, Docker, RDS, Neon, Supabase, or behind an SSH bastion.
Why it’s hereCommunity pick
Official Supabase MCP server to connect AI assistants directly with your Supabase project and allows them to perform tasks like managing tables, fetching config, and querying data.
Why it’s hereCommunity pick
MCP server for interacting with the Supabase platform
Why it’s hereCommunity pick
Local-first codebase intelligence engine. Gives coding agents structured context packets, indexed code/schema facts, and diagnostics over MCP, backed by a local SQLite store — so agents stop rediscovering your repo with raw grep. Optional Postgres/Supabase awareness and a bundled Claude Code plugin.
Why it’s hereCommunity pick
MCP and MCP SSE Server that automatically generate API based on database schema and data. Supports PostgreSQL, Clickhouse, MySQL, Snowflake, BigQuery, Supabase
Why it’s hereCommunity pick
Bug-report triage and fix-dispatch MCP for vibe coders. Ask your AI coding agent for a plain-English diagnosis of any user-reported bug — with evidence, blast radius, and a paste-ready fix prompt — then dispatch an automated GitHub fix PR without a second LLM key. 80+ tools, Supabase-backed, MIT SDK. npx @mushi-mushi/mcp
Why it’s hereCommunity pick
MCP server for PostgreSQL with full read-write support, transactions, and schema inspection. Works with any PostgreSQL instance — local, Supabase, AWS RDS, or self-hosted. Use with Claude, Cursor, Windsurf, and any MCP-compatible AI client.
Why it’s hereCommunity pick
Read-only Postgres/Supabase RLS audit with a rolled-back probe that proves who can read which rows.
Why it’s hereCommunity pick
Read-only security audit for Supabase. Four tools surface RLS gaps, permissive policies, exposed functions and grants; an audit prompt returns scored findings with fix SQL.
Supabase servers range from project-management tools (create projects, run migrations, fetch logs) to plain SQL access against the project database. Connect development projects first: an agent that can run migrations can also drop tables.
Most servers support a read-only mode and project scoping — turn both on unless the task needs writes, and never hand an agent the service_role key for a production project.
This page ranks Supabase MCP servers by real usage across the AllMCPs directory. For generic Postgres access without Supabase-specific tools, see the PostgreSQL page.
Yes, with a server that uses the Supabase Management API and a personal access token. Use it against a development branch or project and review migrations before applying them to production.
Not for production. The service_role key bypasses row-level security. Prefer read-only mode, a scoped access token, or a restricted database role.