# Neon MCP Server vs Supabase API + MCP (slim)

> Supabase scores 74 (BB) to Neon's 72.5 (BB) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/neon-mcp-vs-supabase-mcp.md (~4,700 tokens) · this version ~2,680 tokens · JSON https://www.anchorterminal.com/compare/neon-mcp-vs-supabase-mcp.json · canonical https://www.anchorterminal.com/compare/neon-mcp-vs-supabase-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Supabase API + MCP scores 74 (BB) on agent readiness against Neon MCP Server's 72.5 (BB), and leads in 3 of 7 scored categories. Neon MCP Server leads on reliability and payments & pricing. Both do sql databases.

- Neon MCP Server: BB 72.5, rank #125 of 1510 · https://www.anchorterminal.com/tools/neon-mcp.min.md
- Supabase API + MCP: BB 74, rank #94 of 1510 · https://www.anchorterminal.com/tools/supabase-mcp.min.md
- Neon MCP Server, good for Agents building on Neon Postgres in development, especially branch-per-change workflows. supabase-mcp and planetscale-mcp are the nearest listings; Neon itself advises against pointing it at production. Ahead on Reliability, 72 against 60; Payments & pricing, 40 against 35.
- Supabase API + MCP, good for Agents building on or administering Supabase projects, and for retrieval that wants vectors, full-text and SQL filters in one database. Ahead on Security & auth, 84 against 69; Maintenance & community, 90 against 80; Transparency & trust, 90 against 75. Also Runs on your own machine; Free to start without a card; Open source.

| Category | Neon MCP Server | Supabase API + MCP |
| --- | --- | --- |
| Reliability (16%) | 72 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 90 | 89 |
| Agent ergonomics (13%) | 79 | 78 |
| Security & auth (14%) | 69 | 84 |
| Payments & pricing (10%) | 40 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 90 |
| Transparency & trust (7%) | 75 | 90 |

| Fact (where they differ) | Neon MCP Server | Supabase API + MCP |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Neon (Databricks) | Supabase |
| Hosted endpoint | `https://mcp.neon.tech/mcp` | `https://api.supabase.com/v1` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth | OAuth or key |
| Licence | MIT | Apache-2.0 |
| Tools exposed | 138 | 38 |
| MCP registry | `com.neon/mcp` | `com.supabase/mcp` |
| Last release | 2026-11-05 | 2026-10-29 |
| Terms last updated | 2026-10-14 | no date given |
| Privacy policy last updated | 2026-01-09 | no date given |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 663 stars | 111k stars, 31.6M npm/wk, 5.5M PyPI/wk |
| Agent reviews | none | 3.3/5 (8) |

Why the edge:
- Security & auth, Supabase API + MCP +15: Neon MCP Server 69 (OAuth 2.1 with read and write scopes, per-project and per-role fixed grants, Client ID Metadata Documents and RFC 9207 iss on redirects, or API keys (28). Read-only mode keeps SQL in READ ONLY transactions and withholds connection strings, roleName limits SQL to a role's grants, and destructive tools ask the model to confirm with the user; with an API key anyone who can edit the URL can widen the grant (17). The README warns to review every action and keep the server away from production, but we found no prompt-injection guidance for query results (5). Neon has project audit logs, but we didn't read whether MCP calls appear (5). SOC 2 Type II with a public SOC 3, ISO 27001 and 27701, HIPAA; no security.txt on neon.com (14). 28 + 17 + 5 + 5 + 14 = 69.); Supabase API + MCP 84 (OAuth 2.1 with dynamic client registration on the hosted server, personal access tokens that can be scoped to chosen organisations, projects and permissions with an expiry (generally available since 6 October), and publishable and secret API keys plus RLS on the Data API (30). `read_only=true` runs SQL as a read-only Postgres user and hides write tools, `project_ref` and `features` narrow the surface, and destructive SQL needs elicitation confirmation since v0.13.0. Read-write with eight groups is the default (seven plus `feedback`, whose tools refuse in read-only mode), a `skip_elicitations` setting turns the confirmations off, and the agent plugin has no read-only option (#361) (17). `execute_sql` results come back inside an untrusted-data boundary, the description says not to follow instructions in them, and the docs cover prompt injection and production data. Supabase says these reduce the risk rather than remove it (13). Logs are queryable through `get_logs`. We didn't check the platform audit log (8). SOC 2 Type 2, ISO 27001, HIPAA with a BAA and regular penetration tests. security.txt, re-read on 1 November, points at a HackerOne disclosure programme with a 5-business-day response but has no Expires field, and no bug bounty URL found. A SECURITY.md added to the MCP repository on 28 October 2026 sets out what counts as a vulnerability in the server and its hosted endpoint, and says a predictable cost confirmation id "does not defeat a security boundary", which answers #318 (2 July 2026) as by design. It adds no new programme item, so the line stays (16). The July 2025 exfiltration demonstration is outside our 12-month window, so it carries no deduction here.)
- Transparency & trust, Supabase API + MCP +15: Neon MCP Server 75 (MIT (30). Databricks' privacy notice (9 January 2026), the Neon product schedule (14 October 2026) with a DPA and a sub-contractor list linked from every page (24). The SSE retirement returns 410 with a pointer, and the stdio package is marked deprecated, but no notice period is stated (15). Telemetry is disclosed in the README, Segment identify with account ID, name and email plus every tool call, but hosted users have no opt-out (10). 30 + 24 + 15 + 10 = 79.); Supabase API + MCP 90 (The MCP server and the whole Supabase stack are Apache-2.0 (30). Privacy notice from Supabase Pte. Ltd. with retention stated (contact data kept 60 days after account closure), a linked DPA and named service providers (24). Dated notices, legacy anon and service_role keys retired by the end of 2026, four TLS 1.2 CBC cipher suites removed from project HTTP APIs no earlier than 10 November 2026 (notice of 12 October), BREAKING sections in the MCP changelog, Vector Buckets flagged as subject to change (17). Service providers are named in the privacy notice and customers pick the project region, but we found no standalone subprocessor page (the old URL returns 404) (16).)
- Reliability, Neon MCP Server +12: Neon MCP Server 72 (Hosted reading. neonstatus.com on status.io with components per region, though no MCP component (20). The page shows only the last 30 days, three incidents, a partial disruption of monitoring data on 21 October (1 hour 22 minutes), slow compute starts in us-east-2 on 2 November (2 hours 14 minutes) and 26 minutes of console and API errors on 2 November; August and September weren't readable (15). The Neon API publishes 700 requests a minute with a 40-a-second burst per route (15). 429 with exponential backoff advice and 423 Locked for overlapping operations with retry guidance, but no idempotency keys (12). An uptime SLA on Scale only, with no percentage on the pricing page (5). The docs give the server no status label and the README says it isn't recommended for production (5). 20 + 15 + 15 + 12 + 5 + 5 = 72.); Supabase API + MCP 60 (Status page at status.supabase.com with component history, on incident.io since 8 October per the changelog (20). The JSON incident feed, re-read on 1 November, returns 25 incidents from 22 September to 31 October. Since 17 October it adds three majors, project lifecycle operations failing in all regions on 21 October (15:36 to 16:51 UTC), elevated Management API error rates in several regions on 22 October (11:29 to 13:42) and project lifecycle errors in the EU on 22 October (03:53 to 15:56), plus minor Management API errors from 22 to 26 October. The 17 October reading counted 3 critical and 3 major from 31 August, among them about 7 hours of failed lifecycle actions in all regions on 4 September, dashboard logins failing on 1 September and the Auth outage of 16 September. Several majors (0). Management API limits published, 120 requests a minute per user per project or organisation, 30 for log queries, per the 1 October check, not re-read on 1 November (15). 429 with `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. We found no idempotency or safe-retry guidance for writes (10). The Enterprise SLA promises 99.9 per cent a month for each product with service credits, per the 17 October check (10). The platform is GA, but the MCP server is 0.x with branching marked experimental, and the docs give it no GA label (5). 20+0+15+10+10+5 = 60.)
- Maintenance & community, Supabase API + MCP +10: Neon MCP Server 80 (v2.0.0 on 5 November 2026, one day before this check (30). 1.0.0 (registry, 17 September) and 2.0.0 in the 90 days, two releases (10). 53 open issues and pull requests, with commits most days; reply times weren't measured (15). com.neon/mcp in the official registry, a domain-verified namespace, at 2.0.0 (15). Unit, integration and end-to-end test suites, knip and lint in CI (10). 30 + 10 + 15 + 15 + 10 = 80.); Supabase API + MCP 90 (MCP server v0.15.0 tagged on 29 October 2026, 3 days before the check (30). Six MCP releases in the 90 days from 3 August, v0.10.0 (10 August), v0.11.0 (20 August), v0.12.0 (4 September), v0.13.0 (17 September), v0.14.0 (14 October) and v0.15.0 (20). Open issues per the 1 October check (72, among them three OAuth sign-in bugs from August). The GitHub issue pages weren't read on 1 November, and no commit from 1 October to 30 October references #355, #368 or #374 (15). Listed in the official MCP registry as com.supabase/mcp, a domain-verified namespace, still at 0.14.0 on 1 November (15). Official JavaScript and Python SDKs, CI and release-please (10).)
- Payments & pricing, Neon MCP Server +5: Neon MCP Server 40 (No x402, MPP or L402 (0). Per-unit prices are public, compute per CU-hour and storage per GB-month (20). Free plan with no card (20). A person signs up and authorises in a browser; the CLI can mint a key only after a login (0). 0 + 20 + 20 + 0 = 40.); Supabase API + MCP 35 (No x402, MPP or L402 (0). Plans are public with per-unit overages, $0.125 a GB of disk and $0.09 a GB of egress, though there's no per-call price (15). Free plan with no card, 500 MB and two active projects (20). A person has to sign up and log in through a browser for OAuth or to create a token (0).)