# Neon MCP Server vs Snowflake-managed MCP server (slim)

> Neon scores 72.5 (BB) to Snowflake-managed's 52.7 (D) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.md (~5,150 tokens) · this version ~3,130 tokens · JSON https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.json · canonical https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed
- 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)

Neon MCP Server scores 72.5 (BB) on agent readiness against Snowflake-managed MCP server's 52.7 (D), and leads in 5 of 7 scored categories. Snowflake-managed MCP server leads on security & auth and transparency & trust. Both do sql databases.

- Neon MCP Server: BB 72.5, rank #125 of 1510 · https://www.anchorterminal.com/tools/neon-mcp.min.md
- Snowflake-managed MCP server: D 52.7, rank #978 of 1510 · https://www.anchorterminal.com/tools/snowflake-managed.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 50; Schema & documentation, 90 against 61; Agent ergonomics, 79 against 46; Payments & pricing, 40 against 35; Maintenance & community, 80 against 35. Also Agent-ready, a grade of BB or better; A hosted endpoint, with nothing to install; No incidents deducted, where Snowflake-managed MCP server loses 3 points for them.
- Snowflake-managed MCP server, good for A company that already keeps its data in Snowflake and wants outside MCP clients to query it under existing roles, best through one Cortex Agent tool. Ahead on Security & auth, 77 against 69; Transparency & trust, 84 against 75.

| Category | Neon MCP Server | Snowflake-managed MCP server |
| --- | --- | --- |
| Reliability (16%) | 72 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 90 | 61 |
| Agent ergonomics (13%) | 79 | 46 |
| Security & auth (14%) | 69 | 77 |
| Payments & pricing (10%) | 40 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 35 |
| Transparency & trust (7%) | 75 | 84 |

| Fact (where they differ) | Neon MCP Server | Snowflake-managed MCP server |
| --- | --- | --- |
| Vendor | Neon (Databricks) | Snowflake Inc. |
| Hosted endpoint | `https://mcp.neon.tech/mcp` | no (local only) |
| Auth | OAuth | OAuth or key |
| Pricing | Freemium | Pay per use |
| Licence | MIT | Proprietary service under Snowflake's terms of service |
| Tools exposed | 138 | none |
| MCP registry | `com.neon/mcp` | not listed |
| Last release | 2026-11-05 | 2026-08-20 |
| Terms last updated | 2026-10-14 | 2026-04-16 |
| Privacy policy last updated | 2026-01-09 | 2026-07-01 |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 663 stars | none |

Why the edge:
- Maintenance & community, Neon MCP Server +45: 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.); Snowflake-managed MCP server 35 (Per the 9 October check, not re-read on 4 November (snowflake.com's site terms bar robots). The last dated change to the MCP server is the SSE note of 20 August 2026, 76 days before 4 November, and platform release notes ran to 9 October (20). Of the three dated MCP entries recorded (22 July, 7 August and 20 August 2026), two fall in the 90 days from 6 August, and newer entries couldn't be looked for (0, cause time). A public changelog and a support route through cases and the community, whose answers were not sampled (10). The managed server is not in the official MCP registry, which lists only the separate open-source `io.github.Snowflake-Labs/mcp` (0). Nothing to install. The REST API specification repository was last updated on 10 September 2026 (5). 20+0+10+0+5 = 35.)
- Agent ergonomics, Neon MCP Server +33: Neon MCP Server 79 (138 tools with no grant, far over 30 (5), with category, projectId and readonly to cut the list (plus 10). List tools take limits and cursors from the API, and describe_branch returns a tree (16). API errors return with their kind and status, path errors are tool errors, and unknown categories come back as a notice (16). readOnlyHint and destructiveHint on every definition, and the grant filter tells the model never to run destructive tools autonomously (18). Official TypeScript and Python SDKs for the Neon API; a no-auth tool preview endpoint (14). 15 + 16 + 16 + 18 + 14 = 79.); Snowflake-managed MCP server 46 (The tool list is whatever the operator declares, up to 50 a server, and Snowflake recommends one Cortex Agent tool per server with further servers for other uses (18). The search tool takes `columns` and `limit`. SQL and custom tool responses are cut at 250 KB with no paging, and agent tool responses carry every intermediate step and can pass 200 KB (8). Errors are documented as a symptom table, and `invalid_client` covers both wrong credentials and a network policy block (6). The SQL tool is read-only by default. No `readOnlyHint` or `destructiveHint` annotations and no idempotency support are documented (6). Few required arguments and standard MCP clients work with no SDK, but each client needs a hand-made OAuth integration and some clients can't choose a role (8). Per the 9 October check, not re-read on 4 November.)
- Schema & documentation, Neon MCP Server +29: Neon MCP Server 90 (Every tool has a JSON Schema, many generated from the Neon OpenAPI spec (25). neon.com serves llms.txt and Markdown pages (10). Descriptions say when and when not ("branch_id is a branch id, not a branch name. Call list_branches to resolve a name", "NEVER run autonomously") (18). Typed inputs with enums such as access read_only or read_write, and path arguments checked for . and .. since 2.0.0 (13). Examples in the README and docs, and API 4xx errors classified by kind (11). CHANGELOG with dated releases and a registry version (13). 25 + 10 + 18 + 13 + 11 + 13 = 90.); Snowflake-managed MCP server 61 (No OpenAPI or published schema covers the MCP endpoint, and the snowflake-rest-api-specs repository has no MCP server file. Custom tools carry a JSON Schema the operator writes in `input_schema`, and built-in tools take fixed arguments shown only as examples. The schemas `tools/list` returns were not read (15). llms.txt and a Markdown copy of every docs page (10). Tool names and descriptions are written by the operator, and Snowflake's own examples are one line each, such as "cortex search service for all products" (8). Typed inputs for custom tools, with free-text SQL and a single `message` string for the analyst and agent tools (8). Request and response examples for two tool types, a troubleshooting table and OAuth failure modes, with no JSON-RPC error codes and an empty object as the search response example (8). Dated release notes, behaviour change notes and a stated protocol revision of 2025-11-25 (12). Per the 9 October check, not re-read on 4 November.)
- Reliability, Neon MCP Server +22: 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.); Snowflake-managed MCP server 50 (Graded as a hosted service. Snowflake's site terms (14 April 2025) bar robots, spiders and scrapers on snowflake.com, so the docs, the status page and www.snowflake.com were not re-read on 4 November and the 9 October readings stand. Statuspage at status.snowflake.com with components by cloud region, and no component for Cortex or the MCP server was recorded (15, the value for a vendor status page with no component for the product). Only the front page's 15 days to 9 October were read, with two incidents marked critical (one region for 68 minutes on 25 September 2026, other regions for 35 minutes on 27 September), one marked major (Snowsight connectivity, 6 October) and one minor (8 October). The rest of the window from 6 August is unread and gets no credit, so the incident line is held at the recorded 10. No rate limit for the MCP endpoint found (0). The REST API's OpenAPI files describe 429 and retry with backoff, but the MCP page gives no retry or idempotency guidance (5, partial value held). 99.9 per cent monthly SLA with service credits (10). Generally available since 4 November 2025 (10). 15+10+0+5+10+10 = 50.)
- Transparency & trust, Snowflake-managed MCP server +9: 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.); Snowflake-managed MCP server 84 (Closed service with clear published terms, an acceptable use policy and a consumption table (15). A DPA and Security Addendum of 11 January 2026 with 72-hour incident notice and customer-chosen regions. The DPA says leftover data is deleted promptly after termination without a day count, and the Privacy Notice excludes Customer Data (22). A written behaviour change policy with an eight-week bundle period and dated notes, though the August 2026 MCP change shipped outside it (15). Four sub-processors and 28 affiliates listed with locations and 28 days' notice of additions. AI model providers are not named on the list (16). Per the 9 October check, not re-read on 4 November.)
- Security & auth, Snowflake-managed MCP server +8: 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.); Snowflake-managed MCP server 77 (OAuth 2.0 with PKCE, role scopes, an allowed-roles list, binding to an external identity provider and RFC 9728 metadata. Programmatic access tokens expire (15 days by default, 365 at most), can be rotated and need a network policy by default. No dynamic client registration (28). Each tool needs its own grant, the SQL tool defaults to read-only, and the docs advise a separate least-privileged server for direct SQL. No confirmation step for writes is documented (15). The docs warn about tool poisoning, tool shadowing and recursive loops and cap recursion at 10. Nothing covers instructions arriving in query or search results (6). Account Usage has query, login and access history and a Cortex Agent usage view. No log of MCP tool calls was found (10). security.txt valid to 17 August 2027 with a HackerOne policy, SOC 2 Type II, ISO 27001, HITRUST and FedRAMP per the Security Addendum. The HackerOne page was not read (18). Per the 9 October check, not re-read on 4 November.)