Supabase MCP Server vs Neon MCP Server

When to pick Supabase MCP Server

• Your application already uses Supabase, and you want the assistant to inspect tables, execute SQL and apply schema changes. list_tables, execute_sql and apply_migration cover those tasks within your existing project.
• You need database work alongside application debugging. get_logs, generate_typescript_types and search_docs let the assistant read logs, generate TypeScript types and consult Supabase documentation through the same server.
• You develop against a local Supabase instance managed by the CLI. Its MCP endpoint is available at http://localhost:54321/mcp, though it exposes fewer tools than the hosted service and does not offer OAuth 2.1.
• You are building an integration with Vercel AI SDK and need typed tool inputs and outputs. The package exports createToolSchemas() for client-side validation and inferred TypeScript types, with filters for features, project scope and read-only use.

When to pick Neon MCP Server

• Your database runs on Neon, and you want to test a migration before applying it to the original branch. prepare_database_migration creates a temporary branch; complete_database_migration applies the prepared change and cleans up temporary resources.
• You need to investigate query performance. explain_sql_statement returns execution plans, while prepare_query_tuning tests suggested optimizations on a temporary branch. complete_query_tuning lets you apply or discard them.
• You want an assistant to query one project using a specific Postgres role. Combine projectId, readonly=true and roleName in the connection URL. The role limits SQL privileges; management API tools retain the credential's own access.
• You need a remote agent to authenticate where browser OAuth is unavailable. Neon accepts an API key in the Authorization bearer header when the client supports headers. Neon documents this server for local development and IDE integrations, and advises against production use.

Main differences

• Both provide hosted HTTP endpoints. Supabase also documents CLI-local and self-hosted Supabase connections with reduced tool sets. Neon's managed connection requires no local server installation and uses Streamable HTTP; its SSE endpoint is deprecated.
• Supabase's hosted login uses OAuth with dynamic client registration, without manually creating a personal access token. Neon offers browser OAuth or an API key. Its separate npx neon@latest init setup authenticates with OAuth, then creates an API key and configures the editor.
• Supabase combines SQL and migrations with logs and TypeScript type generation. Neon exposes branch and compute management, schema comparison, database diagnostics and query-tuning workflows. Both include documentation search and branch-based schema rehearsal.
• Supabase filters access with project_ref, read_only=true and features. Neon uses projectId, readonly=true and category, plus roleName for SQL login privileges. Neon OAuth tokens retain the authorized grant; changing URL parameters requires reauthorization to change that grant.
• Supabase's SDK schema helper can omit mutating tools for a read-only connection. Neon documents execution behavior too: run_sql uses a READ ONLY transaction, while run_sql_transaction is unavailable in read-only mode.
• Supabase's optional observer does not automatically receive request or response payloads. Neon documents account identity analytics and tool-call metadata, excluding tool arguments and query results from those events, plus Sentry error reports. These are different telemetry mechanisms, not equivalent privacy guarantees.

Setup

For Supabase, run claude mcp add --transport http supabase https://mcp.supabase.com/mcp in Claude Code. Follow the login prompt and select the organization containing your project.

For Neon, run npx add-mcp https://mcp.neon.tech/mcp to configure detected agents and editors in the workspace. This unfiltered URL exposes every tool category. Refresh or restart the client and complete browser authorization. For organization projects under OAuth, include org_id or project_id in your prompt.