Supabase Alternatives: 4 MCP Servers Like Supabase

Connect AI assistants to Supabase projects for SQL, schema changes, debugging, and Edge Functions. Hosted HTTP setup supports project scoping, read-only access, and selectable feature groups.

Supabase alternatives compared

Supabase MCP Server connects development assistants to Supabase project administration and database work. Its tools span schema inspection, SQL queries, tracked migrations, documentation search, advisory checks, and application configuration. Other groups expose Edge Function source and deployment, project lifecycle operations, and development branches. TypeScript types can be generated from a project's database schema, giving an assistant information it can use while building application code. The hosted service uses an HTTP endpoint, and compatible clients guide users through signing in to the appropriate Supabase organization.

Ranked by shared tags × quality; ties: quality, non-monorepo stars, slug.

Supabase setup notes

Supabase MCP Server's example uses http, while its catalog transports are stdio; use the example's connection type.

Why switch from Supabase

1. Neon MCP Server

Supabase MCP Server and Neon MCP Server share 5 exact tool names: create_branch, create_project, delete_branch, …. Neon MCP Server lists 25 names absent from Supabase MCP Server, including __node_version, compare_database_schema, complete_database_migration. Moving from Supabase MCP Server to Neon MCP Server would also mean rechecking workflows using apply_migration, confirm_cost, deploy_edge_function, which appear only in Supabase MCP Server's list. Supabase MCP Server and Neon MCP Server both list node / stdio. Supabase MCP Server is listed under Apache-2.0, versus MIT for Neon MCP Server. Neon MCP Server's repository has 2,305 fewer stars than Supabase MCP Server (654 versus 2,959). Last pushes: Supabase MCP Server 2026-10-17; Neon MCP Server 2026-10-16.

Neon MCP Server overlaps Supabase on: postgresql.

2. Postgres MCP Pro

Supabase MCP Server and Postgres MCP Pro share 1 exact tool name: execute_sql. Postgres MCP Pro lists 8 names absent from Supabase MCP Server, including analyze_db_health, analyze_query_indexes, analyze_workload_indexes. Moving from Supabase MCP Server to Postgres MCP Pro would also mean rechecking workflows using apply_migration, confirm_cost, create_branch, which appear only in Supabase MCP Server's list. Supabase MCP Server records node; Postgres MCP Pro records python. Supabase MCP Server and Postgres MCP Pro both list stdio. Supabase MCP Server is listed under Apache-2.0, versus MIT for Postgres MCP Pro. Postgres MCP Pro's repository has 444 more stars than Supabase MCP Server (3,403 versus 2,959). Last pushes: Supabase MCP Server 2026-10-17; Postgres MCP Pro 2026-08-17.

Postgres MCP Pro overlaps Supabase on: postgresql.

3. Query MCP for Supabase

Supabase MCP Server records node; Query MCP for Supabase records python. Supabase MCP Server and Query MCP for Supabase both list stdio / Apache-2.0. Query MCP for Supabase's repository has 2,126 fewer stars than Supabase MCP Server (833 versus 2,959). Last pushes: Supabase MCP Server 2026-10-17; Query MCP for Supabase 2026-08-21.

Query MCP for Supabase overlaps Supabase on: supabase.

4. MCP Server for MySQL

Supabase MCP Server and MCP Server for MySQL have no exact tool-name overlap in their recorded lists. MCP Server for MySQL lists 1 name absent from Supabase MCP Server, including mysql_query. Moving from Supabase MCP Server to MCP Server for MySQL would also mean rechecking workflows using apply_migration, confirm_cost, create_branch, which appear only in Supabase MCP Server's list. Supabase MCP Server and MCP Server for MySQL both list node / stdio. Supabase MCP Server is listed under Apache-2.0, versus MIT for MCP Server for MySQL. MCP Server for MySQL's repository has 793 fewer stars than Supabase MCP Server (2,166 versus 2,959). Last pushes: Supabase MCP Server 2026-10-17; MCP Server for MySQL 2026-07-27.

MCP Server for MySQL overlaps Supabase on: read-only.