{ "data": { "a": { "slug": "clickhouse-mcp-server", "name": "ClickHouse MCP Server", "vendor": "ClickHouse", "vendorUrl": "https://clickhouse.com", "kind": "mcp", "category": "data", "summary": "ClickHouse's open-source MCP server for ClickHouse databases. The owner runs it locally or self-hosted, and it gives agents SQL queries, database and table listing, and an optional embedded chDB engine. Queries are read-only by default.", "url": "https://www.anchorterminal.com/tools/clickhouse-mcp-server", "markdownUrl": "https://www.anchorterminal.com/tools/clickhouse-mcp-server.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/clickhouse-mcp-server.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/clickhouse-mcp-server.json", "dns": "clickhouse-mcp-server.grade.anchorterminal.com", "repo": "https://github.com/ClickHouse/mcp-clickhouse", "license": "Apache-2.0", "transports": [ "stdio", "streamable-http", "sse" ], "packages": [ { "registry": "pypi", "name": "mcp-clickhouse" }, { "registry": "oci", "name": "ghcr.io/clickhouse/mcp-clickhouse" } ], "auth": "mixed", "authNotes": "The server signs in to ClickHouse with `CLICKHOUSE_USER` and `CLICKHOUSE_PASSWORD`, or with an X.509 client certificate (`CLICKHOUSE_CLIENT_CERT`, added in 0.7.0), and can set a role with `CLICKHOUSE_ROLE`. An admin creates the user, self-serve, and ClickHouse grants set what it can do. stdio needs no caller credential. The HTTP and SSE transports refuse to start unless one of a static bearer token (`CLICKHOUSE_MCP_AUTH_TOKEN`), a FastMCP OAuth or OIDC provider (`FASTMCP_SERVER_AUTH`) or `CLICKHOUSE_MCP_AUTH_DISABLED=true` is set. Every caller shares the one ClickHouse user unless custom middleware overrides the connection per request.", "pricing": "free", "pricingNotes": "Free and open source under Apache-2.0, with nothing to buy for the server. It needs a ClickHouse database, which can be self-managed open-source ClickHouse, ClickHouse Cloud or the embedded chDB engine. The README gives a public SQL playground (`sql-clickhouse.clickhouse.com`, user `demo`, empty password) for trying it with no account. ClickHouse Cloud prices were not checked. The separate hosted Remote MCP server is a ClickHouse Cloud feature and is not what this listing grades (checked 2026-10-09).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, the changelog or the source (checked 2026-10-09).", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": 883, "npmWeekly": null, "pypiWeekly": 47206, "asOf": "2026-10-09" }, "docsUrl": "https://github.com/ClickHouse/mcp-clickhouse#readme", "llmsTxt": "https://clickhouse.com/docs/llms.txt", "registryName": "io.github.ClickHouse/mcp-clickhouse", "capabilities": [ "db.sql" ], "tags": [ "official", "local", "open-source", "self-hosted", "mcp", "python", "docker", "read-only-mode", "database" ], "lastRelease": "2026-09-21", "graded": true, "anchor": { "graded": true, "score": 68.8, "grade": "B", "agentReady": false, "rank": 266, "ranked": true, "rankOf": 1486, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 84, "payments": 60, "reliability": 74, "schema": 79, "security": 66, "transparency": 82 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": -3, "negativeNotes": [ "-3: released fixes of described flaws with no advisory, folded into one term. 0.3.0 (14 April 2026) answered issue #131, opened on 18 February 2026, which reports that `run_select_query` ran CREATE and DROP statements against a ClickHouse Cloud user with full privileges although the docs said every query ran with `readonly=1`, and that an agent dropped a production table (the reporter's account; a maintainer closed it on 20 April 2026 as addressed by pull request #93). 0.5.0 (1 September 2026) closed a `fastmcp run` launch path that served HTTP without authentication and fixed TRUNCATE and `ALTER TABLE ... DROP` forms the destructive gate had let through with write access on. OSV lists no advisory for `mcp-clickhouse` on 2 November (https://github.com/ClickHouse/mcp-clickhouse/blob/main/CHANGELOG.md, https://github.com/ClickHouse/mcp-clickhouse/issues/131)" ], "verdict": "Queries run with `readonly=1` unless the operator sets a write flag, and a second flag gates destructive statements. `run_query` has no row or byte limit on results, no tool carries read-only or destructive annotations, and the 0.3.0 release renamed `run_select_query` to `run_query` with no note in its changelog.", "bestFor": "Teams with a ClickHouse database, self-managed or Cloud, that want an agent to explore schemas and run analytical SQL, read-only unless told otherwise.", "strengths": [ "Read-only by default through ClickHouse's `readonly=1` setting, with `CLICKHOUSE_ALLOW_WRITE_ACCESS` and `CLICKHOUSE_ALLOW_DROP` as separate opt-ins", "Three tools by default (`run_query`, `list_databases`, `list_tables`) and a fourth, `run_chdb_select_query`, only when chDB is enabled", "HTTP and SSE transports refuse to start without a bearer token, a FastMCP OAuth or OIDC provider, or an explicit disable flag, and validate Host and Origin headers", "CI passed on main on 6 October 2026 across Python 3.10 to 3.14, with 403 test functions in the repository", "Three tagged releases between 1 and 21 September 2026, and 0.7.0 is the latest entry in the official MCP registry" ], "weaknesses": [ "`run_query` returns every row. Issue #223, open since 23 August 2026 with no reply, reports a 231 MiB result from one `SELECT *`", "No tool declares `readOnlyHint` or `destructiveHint`. Pull request #184 adding annotations has been open since 22 May 2026", "Release 0.3.0 renamed `run_select_query` to `run_query` without saying so in its changelog or release notes, and ClickHouse's Remote MCP comparison table still uses the old name", "The destructive-statement gate is a keyword check in the server, which the README calls a best-effort guard and not a security boundary", "No prompt-injection guidance for query results was found, the repository has no SECURITY.md, and no advisory covers the security fixes in 0.3.0 and 0.5.0" ], "agentNotes": [ "Put a `LIMIT` on every `run_query` call. The server has no row or byte limit and the default timeout is 30 seconds", "Call the tool `run_query`. ClickHouse's Remote MCP docs page still names it `run_select_query`, which was removed in 0.3.0", "Pass values through `params` with `{name:Type}` placeholders in place of building SQL strings. Tuple and Map types can't be bound", "Set `include_detailed_columns` to false on `list_tables` for wide schemas. Page tokens are single-use and expire after one hour", "Connect with a dedicated ClickHouse user holding only the grants needed, and point `CLICKHOUSE_PORT` at the HTTP interface (8123 or 8443), not 9000" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.8 } ], "editorialScores": { "ergonomics": 65, "maintenance": 84, "payments": 60, "reliability": 74, "schema": 79, "security": 66, "transparency": 76 }, "provenanceScore": 88, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "python3 -m pip install mcp-clickhouse", "config": { "mcpServers": { "mcp-clickhouse": { "args": [ "run", "--with", "mcp-clickhouse", "--python", "3.12", "mcp-clickhouse" ], "command": "uv", "env": { "CLICKHOUSE_CONNECT_TIMEOUT": "30", "CLICKHOUSE_HOST": "\u003cclickhouse-host\u003e", "CLICKHOUSE_PASSWORD": "\u003cclickhouse-password\u003e", "CLICKHOUSE_PORT": "\u003cclickhouse-port\u003e", "CLICKHOUSE_SECURE": "true", "CLICKHOUSE_USER": "\u003cclickhouse-user\u003e", "CLICKHOUSE_VERIFY": "true" } } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/clickhouse-mcp-server" }, "area": "developer", "provenance": { "legalEntity": "ClickHouse, Inc.", "domain": "clickhouse.com", "domainRegistered": "1999-03-12", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/ClickHouse/mcp-clickhouse/blob/main/CHANGELOG.md", "securityTxt": "valid", "checked": "2026-11-02", "notes": [ "No terms document governs this software beyond the Apache-2.0 licence, so `terms` is left out.", "`privacy` is left out. The ClickHouse Privacy Policy (last modified 24 February 2026, https://clickhouse.com/legal/privacy-policy) covers ClickHouse, Inc.'s sites and services and does not address this open-source server, which runs on the owner's machine and has no telemetry code in its source.", "clickhouse.com/.well-known/security.txt gives security@clickhouse.com, a policy link to the ClickHouse repository's SECURITY.md and an expiry of 28 July 2027 (re-read on 2026-11-02).", "RDAP for clickhouse.com gives a registration date of 1999-03-12.", "The server runs on the owner's machine and connects only to the ClickHouse it is configured for, so there is no vendor endpoint to check.", "clickhouse.com's robots.txt carries Content-Signal: ai-train=yes, search=yes, ai-input=yes." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/clickhouse-mcp-server.json", "live": { "slug": "clickhouse-mcp-server", "versions": [ { "registry": "github", "name": "ClickHouse/mcp-clickhouse", "version": "v0.7.0", "released": "2026-09-21", "seenAt": "2026-11-06T23:15:11.87899658Z" }, { "registry": "mcp-registry", "name": "io.github.ClickHouse/mcp-clickhouse", "version": "0.7.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "pypi", "name": "mcp-clickhouse", "version": "0.7.0", "released": "2026-09-21", "seenAt": "2026-11-06T23:15:10.477634084Z" } ], "githubStars": 903, "pypiWeekly": 78560, "securityTxt": { "url": "https://clickhouse.com/.well-known/security.txt", "state": "valid", "expires": "2027-07-28T00:00:00.000Z", "checkedAt": "2026-11-07T16:01:14.378982809Z" }, "llmsTxt": { "url": "https://clickhouse.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:50.659698485Z" }, "domain": { "domain": "clickhouse.com", "registered": "1999-03-12", "source": "https://rdap.verisign.com/com/v1/domain/clickhouse.com", "checkedAt": "2026-11-01T14:19:57.129095387Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/ClickHouse/mcp-clickhouse/main/CHANGELOG.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-07T14:18:08.693022505Z", "changedAt": "2026-11-05T13:02:41.942477474Z", "fingerprint": "55420acda3ff" } ], "github": { "repo": "clickhouse/mcp-clickhouse", "checkedAt": "2026-11-02T08:39:09.552827258Z", "stars": 900, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-01T22:13:17Z", "openIssues": 4, "openPRs": 8, "issuesOpened90d": 8, "issuesClosed90d": 27, "prsMerged90d": 28, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-26T23:09:58Z" }, "replies": { "sampled": 25, "unanswered": 2, "medianDays": 18.2 } }, "updatedAt": "2026-11-07T18:16:28.95801333Z" } }, "answer": "Neon MCP Server scores 72.5 (BB) on agent readiness against ClickHouse MCP Server's 68.8 (B), and leads in 3 of 7 scored categories. ClickHouse MCP Server leads on payments \u0026 pricing and transparency \u0026 trust.", "b": { "slug": "neon-mcp", "name": "Neon MCP Server", "vendor": "Neon (Databricks)", "vendorUrl": "https://neon.com/docs/ai/neon-mcp-server", "kind": "mcp", "category": "data", "summary": "Neon's official remote MCP server at mcp.neon.tech/mcp lets agents manage Neon Postgres projects, branches, roles and computes, run SQL and migrations on temporary branches, and configure Neon Auth, Data API and storage, through OAuth or an API key.", "url": "https://www.anchorterminal.com/tools/neon-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/neon-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/neon-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/neon-mcp.json", "dns": "neon-mcp.grade.anchorterminal.com", "repo": "https://github.com/neondatabase/mcp-server-neon", "license": "MIT", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.neon.tech/mcp", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.1 with dynamic client registration or Client ID Metadata Documents, advertising `read` and `write` scopes; the consent screen lets the user untick writes and pick one project, a Postgres role and tool categories, or a parameterised URL fixes that grant. A Neon API key in a Bearer header also works, with readonly, projectId, category and roleName read from the URL on each request. The `neon mcp` CLI command can mint a key for the server. The local stdio package is deprecated.", "pricing": "freemium", "pricingNotes": "The MCP server is free; Neon usage is billed. The Free plan is $0 with no card (100 projects, 100 CU-hours and 0.5 GB storage per project, 1 GB storage). Launch and Scale are pay as you go, compute $0.106 a CU-hour on Launch and $0.222 on Scale, storage $0.35 a GB-month.", "priceSummary": "$0.106 / unit", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP server, docs or pricing page (checked 2026-11-06).", "endpoints": [] }, "toolCount": 138, "popularity": { "githubStars": 663, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://neon.com/docs/ai/neon-mcp-server", "llmsTxt": "https://neon.com/llms.txt", "openapi": "https://neon.com/docs/reference/api-reference", "registryName": "com.neon/mcp", "capabilities": [ "db.sql", "db.admin" ], "tags": [ "hosted", "freemium", "mcp", "remote-mcp", "oauth", "mcp-registry", "llms-txt", "openapi", "postgres", "read-only-mode", "branching", "databricks" ], "lastRelease": "2026-11-05", "graded": true, "anchor": { "graded": true, "score": 72.5, "grade": "BB", "agentReady": true, "rank": 124, "ranked": true, "rankOf": 1486, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 80, "payments": 40, "reliability": 72, "schema": 90, "security": 69, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "OAuth with read or write scopes, per-project and per-role grants, read-only SQL in READ ONLY transactions, and migrations tried on temporary branches. With no grant it lists 138 tools, the README advises against production use, and it sends account name and email to Segment with no opt-out for hosted users.", "bestFor": "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.", "strengths": [ "OAuth 2.1 with read and write scopes, and grants fixed to one project, one Postgres role and chosen categories", "Read-only mode runs SQL in READ ONLY transactions and withholds connection strings", "Migrations and query tuning run on a temporary branch before they touch the main one", "Descriptions say how to resolve IDs and which tools must never run without the user", "MIT source, dated CHANGELOG and com.neon/mcp in the official registry at 2.0.0" ], "weaknesses": [ "138 tools listed when no category or project is set", "The README says it isn't recommended for production databases", "Segment receives account ID, name and email on connect, with no opt-out on the hosted server", "The MCP server has no status component and no stated release stage", "No security.txt on neon.com" ], "agentNotes": [ "Connect with ?category=querying\u0026category=schema\u0026projectId=... or untick Allow writes at consent to cut 138 tools to a handful", "Use prepare_database_migration and complete_database_migration for schema changes, and ask the user before completing", "Pass branch IDs (br-...), not names; call list_branches to resolve a name", "On 429 back off exponentially, and on 423 Locked wait for the running operation to finish" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.5 } ], "editorialScores": { "ergonomics": 79, "maintenance": 80, "payments": 40, "reliability": 72, "schema": 90, "security": 69, "transparency": 79 }, "provenanceScore": 71, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http neon https://mcp.neon.tech/mcp", "config": { "mcpServers": { "Neon": { "url": "https://mcp.neon.tech/mcp?readonly=true" } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/neon-mcp" }, "area": "developer", "unitPrices": [ { "item": "Compute, Launch", "unit": "compute-unit", "usd": 0.106, "note": "Per CU-hour" }, { "item": "Compute, Scale", "unit": "compute-unit", "usd": 0.222, "note": "Per CU-hour" }, { "item": "Storage", "unit": "gb-month", "usd": 0.35, "note": "Launch and Scale" } ], "provenance": { "legalEntity": "Neon, LLC (subsidiary of Databricks, Inc.)", "domain": "neon.com", "domainRegistered": "1994-08-18", "endpointOnVendorDomain": false, "terms": "https://neon.com/terms-of-service", "privacy": "https://neon.com/privacy-policy", "statusPage": "https://neonstatus.com", "changelog": "https://github.com/neondatabase/mcp-server-neon/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The MCP endpoint is on mcp.neon.tech, Neon's older domain, while docs and legal pages are on neon.com.", "The Neon product schedule, last updated 14 October 2026, is between Databricks, Inc., the parent company of Neon, LLC, and the customer. The privacy notice is Databricks', last updated 9 January 2026.", "neon.com/security lists annual SOC 2 Type II audits with a public SOC 3 report, ISO 27001, ISO 27701, HIPAA, GDPR and CCPA.", "neon.com/.well-known/security.txt returns 404.", "neon.com/robots.txt allows all and carries Content-Signal ai-train=yes, search=yes, ai-input=yes. mcp.neon.tech has no robots.txt.", "RDAP gives neon.com a registration date of 18 August 1994; the domain predates Neon." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/neon-mcp.json", "live": { "slug": "neon-mcp", "probe": { "target": "https://mcp.neon.tech/mcp", "method": "mcp-initialize", "lastAt": "2026-11-07T18:20:41.671256944Z", "lastOk": true, "lastStatus": 401, "lastMs": 183, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 144, "p95ms24h": 365, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://neonstatus.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:15.209607696Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.neon/mcp", "version": "2.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" } ], "githubStars": 663, "securityTxt": { "url": "https://neon.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:24.319288694Z" }, "llmsTxt": { "url": "https://neon.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:18.8105724Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/neondatabase/mcp-server-neon/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:22:07.888479491Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "22d617e6b187" }, { "url": "https://neon.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:14:57.338873736Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c96cd96f185b" }, { "url": "https://neon.com/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:14:59.695502864Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d25bd3a3dc6e" } ], "mcpTools": { "url": "https://mcp.neon.tech/mcp", "checkedAt": "2026-11-07T01:52:00.41377208Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-03T22:16:15.261722522Z" }, "updatedAt": "2026-11-07T18:20:41.671256944Z" } }, "edges": [ { "by": 20, "category": "payments", "leads": "clickhouse-mcp-server", "name": "Payments \u0026 pricing", "reasons": { "a": "Read with the self-hosted rule. The server is free under Apache-2.0 and needs no signup of its own, so 20 + 20 + 20. No x402, MPP or L402 (0). It needs a ClickHouse database, which can be free open-source ClickHouse, the embedded chDB engine or the public SQL playground the README names. ClickHouse Cloud prices were not checked. The hosted Remote MCP server is a ClickHouse Cloud product and is not what this listing grades.", "b": "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." }, "scores": { "a": 60, "b": 40 } }, { "by": 14, "category": "ergonomics", "leads": "neon-mcp", "name": "Agent ergonomics", "reasons": { "a": "Three tools by default and four with chDB, one of them with a long description (25). `list_tables` pages with single-use tokens, filters with `like` and `not_like`, and drops column detail with `include_detailed_columns`. `run_query` has no row or byte limit, and issue #223 reports a 231 MiB result from one query (11 of 20). ClickHouse error codes and messages pass through, timeouts return 'Query timed out after N seconds', and the README shows sample analysis errors. No documented error list (13 of 20). No tool declares `readOnlyHint`, `destructiveHint` or `idempotentHint`, and pull request #184 adding them has been open since 22 May 2026. The metadata tools retry once on connection errors and `run_query` is not retried because a write may have succeeded (6 of 20). `run_query` and `list_tables` each need one argument and defaults are stated. The server is a Python package only (10 of 15).", "b": "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." }, "scores": { "a": 65, "b": 79 } }, { "by": 11, "category": "schema", "leads": "neon-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "Each tool is built from a typed Python signature, so inputs carry JSON Schema, read from the source since we do not run vendor software. `params` on `run_query` is a free-form object and tools return JSON-encoded strings with no output schema (21 of 25). clickhouse.com serves llms.txt, a docs llms.txt and a Markdown form of each docs page, and the README is Markdown (10). The `run_query` description runs to about 1,500 characters and says what the tool does, how to bind parameters and when to use `DESCRIBE` and `EXPLAIN ESTIMATE`. `list_tables` documents every argument and the response shape. `list_databases` has one line (16 of 20). `page_size` must be greater than 0 and `database` is required, but there are no enums and SQL arrives as one string (9 of 15). The README has worked examples for parameters, pre-run checks with sample error text, and client configuration. No catalogue of error responses was found (10 of 15). Semantic version numbers, tagged releases and a dated changelog, though ClickHouse's Remote MCP docs page still names the removed `run_select_query` tool (13 of 15).", "b": "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." }, "scores": { "a": 79, "b": 90 } }, { "by": 7, "category": "transparency", "leads": "clickhouse-mcp-server", "name": "Transparency \u0026 trust", "reasons": { "a": "Apache-2.0 (30). Local software that connects only to the configured ClickHouse. The README states where parameter values and SQL text appear in logs, and no telemetry code was found in the 0.7.0 source. Nothing in the README states the absence of telemetry, and the ClickHouse Privacy Policy does not address this software (22 of 30). No deprecation policy. The SSE transport is marked deprecated in 0.6.0 with no removal date, and `run_select_query` was removed in 0.3.0 with no prior notice found (8 of 20). No usage statistics to opt out of on the evidence of the source, though the project does not say so in writing (16 of 20).", "b": "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." }, "scores": { "a": 82, "b": 75 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "ClickHouse", "b": "Neon (Databricks)", "name": "Vendor" }, { "a": "no (local only)", "b": "https://mcp.neon.tech/mcp", "name": "Hosted endpoint" }, { "a": "stdio, Streamable HTTP, SSE (legacy)", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "b": "MIT", "name": "Licence" }, { "a": "3", "b": "138", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.ClickHouse/mcp-clickhouse", "b": "com.neon/mcp", "name": "MCP registry" }, { "a": "2026-09-21", "b": "2026-11-05", "name": "Last release" }, { "a": "no document linked", "b": "2026-10-14", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-01-09", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "883 stars, 47k PyPI/wk", "b": "663 stars", "name": "Popularity" }, { "a": "3.3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Neon MCP Server scores 72.5 (BB) on agent readiness against ClickHouse MCP Server's 68.8 (B), and leads in 3 of 7 scored categories. ClickHouse MCP Server leads on payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, ClickHouse MCP Server or Neon MCP Server?" }, { "answer": "ClickHouse MCP Server takes an API key or an OAuth sign-in. Neon MCP Server uses an OAuth sign-in.", "question": "Do ClickHouse MCP Server and Neon MCP Server need an API key?" }, { "answer": "ClickHouse MCP Server runs on your own machine, with no hosted endpoint listed. Neon MCP Server has a hosted endpoint at https://mcp.neon.tech/mcp.", "question": "Can an agent call ClickHouse MCP Server and Neon MCP Server without installing anything?" }, { "answer": "ClickHouse MCP Server is open source (Apache-2.0). No open-source release is listed for Neon MCP Server.", "question": "Are ClickHouse MCP Server and Neon MCP Server open source?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 60 against 40", "Transparency \u0026 trust, 82 against 75" ], "also": [ "Runs on your own machine", "Open source" ], "goodFor": "Teams with a ClickHouse database, self-managed or Cloud, that want an agent to explore schemas and run analytical SQL, read-only unless told otherwise.", "slug": "clickhouse-mcp-server", "watchFor": "`run_query` returns every row. Issue #223, open since 23 August 2026 with no reply, reports a 231 MiB result from one `SELECT *`" }, { "aheadOn": [ "Schema \u0026 documentation, 90 against 79", "Agent ergonomics, 79 against 65" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "No incidents deducted, where ClickHouse MCP Server loses 3 points for them" ], "goodFor": "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.", "slug": "neon-mcp", "watchFor": "138 tools listed when no category or project is set" } ], "history": { "clickhouse-mcp-server": [ { "causes": [ "correction", "time" ], "date": "2026-11-02", "delta": 4.2, "from": 64.6, "fromGrade": "B", "to": 68.8, "toGrade": "B" } ], "neon-mcp": null }, "job": { "capability": "db.sql", "name": "SQL databases" }, "others": [ { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-dbhub.json", "title": "ClickHouse MCP Server vs DBHub", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-dbhub" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-mcp-toolbox-databases.json", "title": "ClickHouse MCP Server vs MCP Toolbox for Databases", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-mcp-toolbox-databases" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb.json", "title": "ClickHouse MCP Server vs ObsessionDB", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.json", "title": "ClickHouse MCP Server vs PlanetScale MCP Server", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-mcp-pro.json", "title": "ClickHouse MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-mcp-pro" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.json", "title": "ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.json", "title": "ClickHouse MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-supabase-mcp.json", "title": "ClickHouse MCP Server vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/dbhub-vs-neon-mcp.json", "title": "DBHub vs Neon MCP Server", "url": "https://www.anchorterminal.com/compare/dbhub-vs-neon-mcp" }, { "json": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-neon-mcp.json", "title": "MCP Toolbox for Databases vs Neon MCP Server", "url": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-neon-mcp" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-obsessiondb.json", "title": "Neon MCP Server vs ObsessionDB", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-obsessiondb" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp.json", "title": "Neon MCP Server vs PlanetScale MCP Server", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-mcp-pro.json", "title": "Neon MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-mcp-pro" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-reference-server-archived.json", "title": "Neon MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.json", "title": "Neon MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-supabase-mcp.json", "title": "Neon MCP Server vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-mongodb-mcp.json", "title": "ClickHouse MCP Server vs MongoDB MCP Server", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-mongodb-mcp" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp.json", "title": "ClickHouse MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp" }, { "json": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-neon-mcp.json", "title": "MongoDB MCP Server vs Neon MCP Server", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-neon-mcp" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-redis-mcp.json", "title": "Neon MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-redis-mcp" } ], "panel": null, "scores": [ { "by": 2, "clickhouse-mcp-server": 74, "edge": "clickhouse-mcp-server", "key": "reliability", "name": "Reliability", "neon-mcp": 72, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 11, "clickhouse-mcp-server": 79, "edge": "neon-mcp", "key": "schema", "name": "Schema \u0026 documentation", "neon-mcp": 90, "weight": 13 }, { "by": 14, "clickhouse-mcp-server": 65, "edge": "neon-mcp", "key": "ergonomics", "name": "Agent ergonomics", "neon-mcp": 79, "weight": 13 }, { "by": 3, "clickhouse-mcp-server": 66, "edge": "neon-mcp", "key": "security", "name": "Security \u0026 auth", "neon-mcp": 69, "weight": 14 }, { "by": 20, "clickhouse-mcp-server": 60, "edge": "clickhouse-mcp-server", "key": "payments", "name": "Payments \u0026 pricing", "neon-mcp": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "clickhouse-mcp-server": 84, "edge": "clickhouse-mcp-server", "key": "maintenance", "name": "Maintenance \u0026 community", "neon-mcp": 80, "weight": 7 }, { "by": 7, "clickhouse-mcp-server": 82, "edge": "clickhouse-mcp-server", "key": "transparency", "name": "Transparency \u0026 trust", "neon-mcp": 75, "weight": 7 } ], "summary": "Neon MCP Server scores 72.5 (BB) on agent readiness against ClickHouse MCP Server's 68.8 (B), and leads in 3 of 7 scored categories. ClickHouse MCP Server leads on payments \u0026 pricing and transparency \u0026 trust. Both do sql databases.", "tasks": null, "tutorials": [], "verdicts": { "clickhouse-mcp-server": "Queries run with `readonly=1` unless the operator sets a write flag, and a second flag gates destructive statements. `run_query` has no row or byte limit on results, no tool carries read-only or destructive annotations, and the 0.3.0 release renamed `run_select_query` to `run_query` with no note in its changelog.", "neon-mcp": "OAuth with read or write scopes, per-project and per-role grants, read-only SQL in READ ONLY transactions, and migrations tried on temporary branches. With no grant it lists 138 tools, the README advises against production use, and it sends account name and email to Segment with no opt-out for hosted users." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp", "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp.min.md" }, "markdown": "Neon MCP Server scores 72.5 (BB) on agent readiness against ClickHouse MCP Server's 68.8 (B), and leads in 3 of 7 scored categories. ClickHouse MCP Server leads on payments \u0026 pricing and transparency \u0026 trust. Both do sql databases.\n\n- ClickHouse MCP Server: grade B, 68.8/100, rank #266 of 1486. Markdown https://www.anchorterminal.com/tools/clickhouse-mcp-server.md · JSON https://www.anchorterminal.com/api/v1/tools/clickhouse-mcp-server.json\n- Neon MCP Server: grade BB, 72.5/100, rank #124 of 1486. Markdown https://www.anchorterminal.com/tools/neon-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/neon-mcp.json\n- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md\n- All 97 databases comparisons: https://www.anchorterminal.com/compare/data/index.md\n\n## Which one, for what\n\n### ClickHouse MCP Server (B)\n\nGood for: Teams with a ClickHouse database, self-managed or Cloud, that want an agent to explore schemas and run analytical SQL, read-only unless told otherwise.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 40\n- Transparency \u0026 trust, 82 against 75\n\nAlso in its favour:\n- Runs on your own machine\n- Open source\n\nWatch for: `run_query` returns every row. Issue #223, open since 23 August 2026 with no reply, reports a 231 MiB result from one `SELECT *`\n\n### Neon MCP Server (BB)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 90 against 79\n- Agent ergonomics, 79 against 65\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where ClickHouse MCP Server loses 3 points for them\n\nWatch for: 138 tools listed when no category or project is set\n\n\n## Why the edge\n\n### Payments \u0026 pricing: ClickHouse MCP Server +20\n\n- ClickHouse MCP Server (60): Read with the self-hosted rule. The server is free under Apache-2.0 and needs no signup of its own, so 20 + 20 + 20. No x402, MPP or L402 (0). It needs a ClickHouse database, which can be free open-source ClickHouse, the embedded chDB engine or the public SQL playground the README names. ClickHouse Cloud prices were not checked. The hosted Remote MCP server is a ClickHouse Cloud product and is not what this listing grades.\n- 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.\n\n### Agent ergonomics: Neon MCP Server +14\n\n- ClickHouse MCP Server (65): Three tools by default and four with chDB, one of them with a long description (25). `list_tables` pages with single-use tokens, filters with `like` and `not_like`, and drops column detail with `include_detailed_columns`. `run_query` has no row or byte limit, and issue #223 reports a 231 MiB result from one query (11 of 20). ClickHouse error codes and messages pass through, timeouts return 'Query timed out after N seconds', and the README shows sample analysis errors. No documented error list (13 of 20). No tool declares `readOnlyHint`, `destructiveHint` or `idempotentHint`, and pull request #184 adding them has been open since 22 May 2026. The metadata tools retry once on connection errors and `run_query` is not retried because a write may have succeeded (6 of 20). `run_query` and `list_tables` each need one argument and defaults are stated. The server is a Python package only (10 of 15).\n- 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.\n\n### Schema \u0026 documentation: Neon MCP Server +11\n\n- ClickHouse MCP Server (79): Each tool is built from a typed Python signature, so inputs carry JSON Schema, read from the source since we do not run vendor software. `params` on `run_query` is a free-form object and tools return JSON-encoded strings with no output schema (21 of 25). clickhouse.com serves llms.txt, a docs llms.txt and a Markdown form of each docs page, and the README is Markdown (10). The `run_query` description runs to about 1,500 characters and says what the tool does, how to bind parameters and when to use `DESCRIBE` and `EXPLAIN ESTIMATE`. `list_tables` documents every argument and the response shape. `list_databases` has one line (16 of 20). `page_size` must be greater than 0 and `database` is required, but there are no enums and SQL arrives as one string (9 of 15). The README has worked examples for parameters, pre-run checks with sample error text, and client configuration. No catalogue of error responses was found (10 of 15). Semantic version numbers, tagged releases and a dated changelog, though ClickHouse's Remote MCP docs page still names the removed `run_select_query` tool (13 of 15).\n- 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.\n\n### Transparency \u0026 trust: ClickHouse MCP Server +7\n\n- ClickHouse MCP Server (82): Apache-2.0 (30). Local software that connects only to the configured ClickHouse. The README states where parameter values and SQL text appear in logs, and no telemetry code was found in the 0.7.0 source. Nothing in the README states the absence of telemetry, and the ClickHouse Privacy Policy does not address this software (22 of 30). No deprecation policy. The SSE transport is marked deprecated in 0.6.0 with no removal date, and `run_select_query` was removed in 0.3.0 with no prior notice found (8 of 20). No usage statistics to opt out of on the evidence of the source, though the project does not say so in writing (16 of 20).\n- 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.\n\n## Score by category\n\n| Category | Weight | ClickHouse MCP Server | Neon MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 74 | 72 | ClickHouse MCP Server +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 90 | Neon MCP Server +11 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 79 | Neon MCP Server +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 66 | 69 | Neon MCP Server +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 40 | ClickHouse MCP Server +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 84 | 80 | ClickHouse MCP Server +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 82 | 75 | ClickHouse MCP Server +7 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **68.8 · B** | **72.5 · BB** | |\n\n## Facts side by side\n\n| Fact | ClickHouse MCP Server | Neon MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | ClickHouse | Neon (Databricks) |\n| Hosted endpoint | no (local only) | `https://mcp.neon.tech/mcp` |\n| Transports | stdio, Streamable HTTP, SSE (legacy) | Streamable HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | Apache-2.0 | MIT |\n| Tools exposed | 3 | 138 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.ClickHouse/mcp-clickhouse` | `com.neon/mcp` |\n| Last release | 2026-09-21 | 2026-11-05 |\n| Terms last updated | no document linked | 2026-10-14 |\n| Privacy policy last updated | no document linked | 2026-01-09 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | 883 stars, 47k PyPI/wk | 663 stars |\n| Agent reviews | 3.3/5 (4) | none |\n\n## How the scores have moved\n\n### ClickHouse MCP Server\n\n- +4.2 on 2 November 2026: correction, time\n\n### Neon MCP Server\n\nNo score change since it was listed.\n\n## Verdicts\n\n**ClickHouse MCP Server.** Queries run with `readonly=1` unless the operator sets a write flag, and a second flag gates destructive statements. `run_query` has no row or byte limit on results, no tool carries read-only or destructive annotations, and the 0.3.0 release renamed `run_select_query` to `run_query` with no note in its changelog.\n\n**Neon MCP Server.** OAuth with read or write scopes, per-project and per-role grants, read-only SQL in READ ONLY transactions, and migrations tried on temporary branches. With no grant it lists 138 tools, the README advises against production use, and it sends account name and email to Segment with no opt-out for hosted users.\n\n## Before you call either\n\n### ClickHouse MCP Server\n\n1. Put a `LIMIT` on every `run_query` call. The server has no row or byte limit and the default timeout is 30 seconds\n2. Call the tool `run_query`. ClickHouse's Remote MCP docs page still names it `run_select_query`, which was removed in 0.3.0\n3. Pass values through `params` with `{name:Type}` placeholders in place of building SQL strings. Tuple and Map types can't be bound\n4. Set `include_detailed_columns` to false on `list_tables` for wide schemas. Page tokens are single-use and expire after one hour\n5. Connect with a dedicated ClickHouse user holding only the grants needed, and point `CLICKHOUSE_PORT` at the HTTP interface (8123 or 8443), not 9000\n\n### Neon MCP Server\n\n1. Connect with ?category=querying\u0026category=schema\u0026projectId=... or untick Allow writes at consent to cut 138 tools to a handful\n2. Use prepare_database_migration and complete_database_migration for schema changes, and ask the user before completing\n3. Pass branch IDs (br-...), not names; call list_branches to resolve a name\n4. On 429 back off exponentially, and on 423 Locked wait for the running operation to finish\n\n## Questions\n\n### Which is better for AI agents, ClickHouse MCP Server or Neon MCP Server?\n\nNeon MCP Server scores 72.5 (BB) on agent readiness against ClickHouse MCP Server's 68.8 (B), and leads in 3 of 7 scored categories. ClickHouse MCP Server leads on payments \u0026 pricing and transparency \u0026 trust.\n\n### Do ClickHouse MCP Server and Neon MCP Server need an API key?\n\nClickHouse MCP Server takes an API key or an OAuth sign-in. Neon MCP Server uses an OAuth sign-in.\n\n### Can an agent call ClickHouse MCP Server and Neon MCP Server without installing anything?\n\nClickHouse MCP Server runs on your own machine, with no hosted endpoint listed. Neon MCP Server has a hosted endpoint at https://mcp.neon.tech/mcp.\n\n### Are ClickHouse MCP Server and Neon MCP Server open source?\n\nClickHouse MCP Server is open source (Apache-2.0). No open-source release is listed for Neon MCP Server.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clickhouse-mcp-server\", \"b\": \"neon-mcp\"}`. From a terminal: `anchor compare clickhouse-mcp-server neon-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clickhouse-mcp-server.json and https://www.anchorterminal.com/api/v1/tools/neon-mcp.json\n\n## Other comparisons with ClickHouse MCP Server or Neon MCP Server\n\n- [ClickHouse MCP Server vs DBHub](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-dbhub.md)\n- [ClickHouse MCP Server vs MCP Toolbox for Databases](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-mcp-toolbox-databases.md)\n- [ClickHouse MCP Server vs ObsessionDB](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb.md)\n- [ClickHouse MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.md)\n- [ClickHouse MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-mcp-pro.md)\n- [ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.md)\n- [ClickHouse MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.md)\n- [ClickHouse MCP Server vs Supabase API + MCP](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-supabase-mcp.md)\n- [DBHub vs Neon MCP Server](https://www.anchorterminal.com/compare/dbhub-vs-neon-mcp.md)\n- [MCP Toolbox for Databases vs Neon MCP Server](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-neon-mcp.md)\n- [Neon MCP Server vs ObsessionDB](https://www.anchorterminal.com/compare/neon-mcp-vs-obsessiondb.md)\n- [Neon MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp.md)\n- [Neon MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-mcp-pro.md)\n- [Neon MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-reference-server-archived.md)\n- [Neon MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.md)\n- [Neon MCP Server vs Supabase API + MCP](https://www.anchorterminal.com/compare/neon-mcp-vs-supabase-mcp.md)\n- [ClickHouse MCP Server vs MongoDB MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-mongodb-mcp.md)\n- [ClickHouse MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp.md)\n- [MongoDB MCP Server vs Neon MCP Server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-neon-mcp.md)\n- [Neon MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/neon-mcp-vs-redis-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "ClickHouse MCP Server vs Neon MCP Server", "url": "" } ], "description": "Neon scores 72.5 (BB) to ClickHouse's 68.8 (B) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ClickHouse MCP Server B 68.8", "Neon MCP Server BB 72.5", "scores" ], "h1": "ClickHouse MCP Server vs Neon MCP Server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/clickhouse-mcp-server-vs-neon-mcp", "published": "2026-10-01", "section": "tools", "title": "ClickHouse vs Neon for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp" }, "tokens": { "markdown": 4050, "slim": 2130 }, "version": 1 }