{ "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", "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": 64.6, "grade": "B", "agentReady": false, "rank": 345, "ranked": true, "rankOf": 950, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 94, "payments": 60, "reliability": 74, "schema": 79, "security": 66, "transparency": 82 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -8, "negativeNotes": [ "-3: release 0.3.0 on 14 April 2026 renamed the `run_select_query` tool to `run_query` (commit d82fc87, pull request #93). Neither the changelog entry nor the GitHub release notes for 0.3.0 mention the rename, and ClickHouse's Remote MCP docs page still names the old tool (https://github.com/ClickHouse/mcp-clickhouse/blob/main/CHANGELOG.md).", "-3: issue #131, opened on 18 February 2026, 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. This is the reporter's account. A maintainer closed it on 20 April 2026 as addressed by pull request #93 in 0.3.0. No advisory was published, and the fix shipped, so a reduced deduction (https://github.com/ClickHouse/mcp-clickhouse/issues/131).", "-2: 0.5.0 on 1 September 2026 closed a `fastmcp run` launch path that served HTTP without authentication and fixed TRUNCATE and `ALTER TABLE ... DROP` forms that the destructive gate had let through with write access on. Both are described in the changelog and fixed, with no advisory, so a reduced deduction (https://github.com/ClickHouse/mcp-clickhouse/blob/main/CHANGELOG.md)." ], "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", "Four tagged releases between 17 July 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 docs page 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": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.6 } ], "editorialScores": { "ergonomics": 65, "maintenance": 94, "payments": 60, "reliability": 74, "schema": 79, "security": 66, "transparency": 76 }, "provenanceScore": 87 }, "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-10-09", "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.", "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." ], "score": 87 }, "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-10-09T16:45:37.005577252Z" }, { "registry": "pypi", "name": "mcp-clickhouse", "version": "0.7.0", "released": "2026-09-21", "seenAt": "2026-10-09T16:45:36.761584684Z" } ], "githubStars": 883, "pypiWeekly": 49925, "securityTxt": { "url": "https://clickhouse.com/.well-known/security.txt", "state": "valid", "expires": "2027-07-28T00:00:00.000Z", "checkedAt": "2026-10-09T15:39:17.233983608Z" }, "llmsTxt": { "url": "https://clickhouse.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:01:36.103621843Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/ClickHouse/mcp-clickhouse/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:44:23.144194276Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b42b96107c3d" } ], "updatedAt": "2026-10-09T18:44:23.144194276Z" } }, "answer": "PlanetScale MCP Server scores 66.4 (B) on agent readiness against ClickHouse MCP Server's 64.6 (B), and leads in 3 of 7 scored categories. ClickHouse MCP Server leads on reliability, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "planetscale-mcp", "name": "PlanetScale MCP Server", "vendor": "PlanetScale", "vendorUrl": "https://planetscale.com", "kind": "mcp", "category": "data", "summary": "PlanetScale's hosted MCP server connects agents to PlanetScale Postgres, Vitess and Neki databases. Its 25 tools cover organisations, branches, schema, read and write SQL, Insights data, Postgres logs, invoices and documentation search, with OAuth or a service token.", "url": "https://www.anchorterminal.com/tools/planetscale-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/planetscale-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/planetscale-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/planetscale-mcp.json", "repo": "https://github.com/planetscale/mcp-server", "license": "Proprietary hosted service under PlanetScale's Terms of Service. The 13 tools in planetscale/mcp-server are Apache-2.0", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.pscale.dev/mcp/planetscale", "packages": [], "auth": "mixed", "authNotes": "OAuth by default. Each MCP client registers as an OAuth application and the person signs in and chooses no, read-only or full access per organisation or per database, with payment-method access set separately. For CI and headless clients a service token secret (`pscale_tkn_`) goes in an `Authorization: Bearer` header, with permissions granted on the token in organisation settings. Claude.ai, Claude for desktop, Claude Managed Agents and Notion accept OAuth only. Access is self-serve after a person signs up.", "pricing": "paid", "pricingNotes": "No charge for the MCP server was found beyond the database plan, and a PlanetScale database is needed for most tools. No free tier or trial was found, and all plans need a payment method on file. Clusters are priced by month, from $5 for a single-node Postgres PS-5 in AWS us-east-1, with storage, backups and egress billed separately (https://planetscale.com/pricing.md, checked 2026-10-09).", "priceSummary": "$5 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP docs, the pricing page or the tool source (checked 2026-10-09).", "endpoints": [] }, "toolCount": 25, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://planetscale.com/docs/mcp-server", "llmsTxt": "https://planetscale.com/docs/llms.txt", "openapi": "https://planetscale.com/docs/openapi.yaml", "registryName": "io.github.planetscale/mcp-server", "capabilities": [ "db.sql", "db.admin" ], "tags": [ "official", "hosted", "mcp", "oauth", "read-only-mode", "paid", "postgres", "mysql", "llms-txt", "openapi", "status-page", "soc2", "database" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 66.4, "grade": "B", "agentReady": false, "rank": 292, "ranked": true, "rankOf": 950, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 80, "payments": 15, "reliability": 63, "schema": 82, "security": 77, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "OAuth scopes set no, read-only or full database access per organisation or database, each query runs on a credential created and deleted for that call, and an insights-only endpoint drops both SQL tools. Destructive statements are gated by a flag the model sets itself, no rate limit was found, and every plan needs a card.", "bestFor": "Agents that inspect and tune an existing PlanetScale database, using Insights, schema recommendations, error patterns and logs, with SQL when granted.", "strengths": [ "OAuth scopes grant no, read-only or full access per organisation or per database, and administrators can cap query access for all members since 8 October 2026", "Each query uses a database credential created for that call and deleted afterwards, and read queries run under a reader role", "An insights-only endpoint omits `planetscale_execute_read_query` and `planetscale_execute_write_query`", "The 13 tools published as source carry `readOnlyHint` and `destructiveHint`, checked by a test in the repository", "Published SLA of 99.99 per cent for single-region and 99.999 per cent for multi-region clusters, with service credits" ], "weaknesses": [ "DELETE and DDL confirmation is a `confirm_destructive` flag the model sets, not a prompt the client shows the person", "The write-query check matches the start of the statement by regular expression, so a statement behind a leading comment or a type it does not list is not matched, per the source", "No rate limit for the MCP server or the API was found. The OpenAPI file lists 429 with no figures", "No free tier. The billing docs say every plan needs a payment method on file", "The hosted server and 12 of its 25 tools are closed. The repository has no tags, changelog or CI workflow", "PlanetScale's website terms forbid robots and other automatic retrieval of the site. Recorded as a fact, and it matters before any probe is run" ], "agentNotes": [ "Use `https://mcp.pscale.dev/mcp/planetscale-insights-only` when the task needs no SQL. It omits both query tools", "Pass `organization`, `database` and `branch` on every query call. Record them in `AGENTS.md` to skip the listing calls", "Show the person the exact DELETE or DDL statement and get approval before setting `confirm_destructive: true`", "Keep queries under 50 seconds and add your own `LIMIT`. The query tools cancel at 50 seconds and return every row", "For a service token send `Authorization: Bearer pscale_tkn_...` with the secret only. The `id:secret` form is rejected" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 66.4 } ], "editorialScores": { "ergonomics": 74, "maintenance": 80, "payments": 15, "reliability": 63, "schema": 82, "security": 77, "transparency": 66 }, "provenanceScore": 73 }, "connect": { "claudeCode": "claude mcp add --transport http \"planetscale\" https://mcp.pscale.dev/mcp/planetscale", "config": { "mcpServers": { "planetscale": { "url": "https://mcp.pscale.dev/mcp/planetscale" } } }, "headless": { "mcpServers": { "planetscale": { "headers": { "Authorization": "Bearer ${env:PLANETSCALE_API_TOKEN}" }, "url": "https://mcp.pscale.dev/mcp/planetscale" } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/planetscale-mcp" }, "area": "developer", "unitPrices": [ { "item": "Postgres PS-5, single node", "unit": "month", "usd": 5, "note": "AWS us-east-1, storage, backups and egress extra" }, { "item": "Postgres PS-5, primary and two replicas", "unit": "month", "usd": 15, "note": "AWS us-east-1, storage, backups and egress extra" }, { "item": "Vitess PS-10, primary and two replicas", "unit": "month", "usd": 39, "note": "AWS us-east-1, storage extra" } ], "provenance": { "legalEntity": "PlanetScale, Inc.", "domain": "planetscale.com", "domainRegistered": "2011-10-06", "endpointOnVendorDomain": false, "terms": "https://planetscale.com/legal/agreement", "privacy": "https://planetscale.com/legal/privacy", "statusPage": "https://www.planetscalestatus.com", "changelog": "https://planetscale.com/changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The MCP server answers at mcp.pscale.dev, a second domain. PlanetScale's own docs name the host, and its response headers name Gram, Speakeasy's hosting platform.", "`terms` is the Terms of Service (last updated 25 August 2026), which the Website Terms of Service name as governing the product. The website terms at /legal/siteterms are a separate document.", "The Privacy Policy (last updated 23 July 2026) names PlanetScale Inc. and says data processed for a customer as a processor is governed by the DPA, which was not read.", "planetscale.com/.well-known/security.txt returns 404. The docs publish a vulnerability disclosure policy with security@planetscale.com.", "The site footer and the terms name PlanetScale, Inc., 535 Mission Street, San Francisco.", "RDAP for planetscale.com gives a registration date of 2011-10-06 and Squarespace Domains II LLC as registrar.", "robots.txt on planetscale.com allows every path with `Content-Signal: ai-input=yes`. robots.txt on mcp.pscale.dev, www.planetscalestatus.com and registry.modelcontextprotocol.io answered 404, and on rdap.verisign.com 400." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/planetscale-mcp.json", "live": { "slug": "planetscale-mcp", "probe": { "target": "https://mcp.pscale.dev/mcp/planetscale", "method": "mcp-initialize", "lastAt": "2026-10-10T02:55:06.241976285Z", "lastOk": true, "lastStatus": 401, "lastMs": 479, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 478, "p95ms24h": 565, "samples24h": 115, "samples30d": 115, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 30, "ok": 30 } ] }, "vendorStatus": { "page": "https://www.planetscalestatus.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T02:50:43.207740175Z" }, "githubStars": 5, "pages": [ { "url": "https://planetscale.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:43:26.437312947Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "20717b5a337c" }, { "url": "https://planetscale.com/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:43:32.591327194Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "11e88e07e991" }, { "url": "https://planetscale.com/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:43:30.563115979Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cfed82900758" }, { "url": "https://planetscale.com/legal/agreement", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:43:28.549006312Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e5e3ad1fe941" } ], "mcpTools": { "url": "https://mcp.pscale.dev/mcp/planetscale", "checkedAt": "2026-10-09T21:40:47.427881901Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:47.427881901Z" }, "updatedAt": "2026-10-10T02:55:06.241976285Z" } }, "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "ClickHouse", "b": "PlanetScale", "name": "Vendor" }, { "a": "no (local only)", "b": "https://mcp.pscale.dev/mcp/planetscale", "name": "Hosted endpoint" }, { "a": "stdio, Streamable HTTP, SSE (legacy)", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "b": "Proprietary hosted service under PlanetScale's Terms of Service. The 13 tools in planetscale/mcp-server are Apache-2.0", "name": "Licence" }, { "a": "3", "b": "25", "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": "io.github.planetscale/mcp-server", "name": "MCP registry" }, { "a": "2026-09-21", "b": "2026-10-08", "name": "Last release" }, { "a": "no document linked", "b": "no date given", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "883 stars, 47k PyPI/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "PlanetScale MCP Server scores 66.4 (B) on agent readiness against ClickHouse MCP Server's 64.6 (B), and leads in 3 of 7 scored categories. ClickHouse MCP Server leads on reliability, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, ClickHouse MCP Server or PlanetScale MCP Server?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do ClickHouse MCP Server and PlanetScale MCP Server need an API key?" }, { "answer": "ClickHouse MCP Server runs on your own machine, with no hosted endpoint listed. PlanetScale MCP Server has a hosted endpoint at https://mcp.pscale.dev/mcp/planetscale.", "question": "Can an agent call ClickHouse MCP Server and PlanetScale MCP Server without installing anything?" }, { "answer": "ClickHouse MCP Server is open source (Apache-2.0). No open-source release is listed for PlanetScale MCP Server.", "question": "Are ClickHouse MCP Server and PlanetScale MCP Server open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 74 against 63", "Payments \u0026 pricing, 60 against 15", "Maintenance \u0026 community, 94 against 80", "Transparency \u0026 trust, 82 against 70" ], "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": [ "Agent ergonomics, 74 against 65", "Security \u0026 auth, 77 against 66" ], "also": [ "A hosted endpoint, with nothing to install", "No incidents deducted, where ClickHouse MCP Server loses 8 points for them" ], "goodFor": "Agents that inspect and tune an existing PlanetScale database, using Insights, schema recommendations, error patterns and logs, with SQL when granted.", "slug": "planetscale-mcp", "watchFor": "DELETE and DDL confirmation is a `confirm_destructive` flag the model sets, not a prompt the client shows the person" } ], "job": { "capability": "db.sql", "name": "SQL databases" }, "others": [ { "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/planetscale-mcp-vs-postgres-mcp-pro.json", "title": "PlanetScale MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-mcp-pro" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived.json", "title": "PlanetScale MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed.json", "title": "PlanetScale MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-supabase-mcp.json", "title": "PlanetScale MCP Server vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/planetscale-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-planetscale-mcp.json", "title": "MongoDB MCP Server vs PlanetScale MCP Server", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-planetscale-mcp" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp.json", "title": "PlanetScale MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp" } ], "scores": [ { "by": 11, "clickhouse-mcp-server": 74, "edge": "clickhouse-mcp-server", "key": "reliability", "name": "Reliability", "planetscale-mcp": 63, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 3, "clickhouse-mcp-server": 79, "edge": "planetscale-mcp", "key": "schema", "name": "Schema \u0026 documentation", "planetscale-mcp": 82, "weight": 13 }, { "by": 9, "clickhouse-mcp-server": 65, "edge": "planetscale-mcp", "key": "ergonomics", "name": "Agent ergonomics", "planetscale-mcp": 74, "weight": 13 }, { "by": 11, "clickhouse-mcp-server": 66, "edge": "planetscale-mcp", "key": "security", "name": "Security \u0026 auth", "planetscale-mcp": 77, "weight": 14 }, { "by": 45, "clickhouse-mcp-server": 60, "edge": "clickhouse-mcp-server", "key": "payments", "name": "Payments \u0026 pricing", "planetscale-mcp": 15, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 14, "clickhouse-mcp-server": 94, "edge": "clickhouse-mcp-server", "key": "maintenance", "name": "Maintenance \u0026 community", "planetscale-mcp": 80, "weight": 7 }, { "by": 12, "clickhouse-mcp-server": 82, "edge": "clickhouse-mcp-server", "key": "transparency", "name": "Transparency \u0026 trust", "planetscale-mcp": 70, "weight": 7 } ], "summary": "PlanetScale MCP Server scores 66.4 (B) on agent readiness against ClickHouse MCP Server's 64.6 (B), and leads in 3 of 7 scored categories. ClickHouse MCP Server leads on reliability, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. Both do sql databases.", "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.", "planetscale-mcp": "OAuth scopes set no, read-only or full database access per organisation or database, each query runs on a credential created and deleted for that call, and an insights-only endpoint drops both SQL tools. Destructive statements are gated by a flag the model sets itself, no rate limit was found, and every plan needs a card." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp", "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.md", "slim": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.min.md" }, "markdown": "PlanetScale MCP Server scores 66.4 (B) on agent readiness against ClickHouse MCP Server's 64.6 (B), and leads in 3 of 7 scored categories. ClickHouse MCP Server leads on reliability, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. Both do sql databases.\n\n- ClickHouse MCP Server: grade B, 64.6/100, rank #345 of 950. Markdown https://www.anchorterminal.com/tools/clickhouse-mcp-server.md · JSON https://www.anchorterminal.com/api/v1/tools/clickhouse-mcp-server.json\n- PlanetScale MCP Server: grade B, 66.4/100, rank #292 of 950. Markdown https://www.anchorterminal.com/tools/planetscale-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/planetscale-mcp.json\n- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md\n- All 43 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- Reliability, 74 against 63\n- Payments \u0026 pricing, 60 against 15\n- Maintenance \u0026 community, 94 against 80\n- Transparency \u0026 trust, 82 against 70\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### PlanetScale MCP Server (B)\n\nGood for: Agents that inspect and tune an existing PlanetScale database, using Insights, schema recommendations, error patterns and logs, with SQL when granted.\n\nAhead on:\n- Agent ergonomics, 74 against 65\n- Security \u0026 auth, 77 against 66\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where ClickHouse MCP Server loses 8 points for them\n\nWatch for: DELETE and DDL confirmation is a `confirm_destructive` flag the model sets, not a prompt the client shows the person\n\n\n## Score by category\n\n| Category | Weight | ClickHouse MCP Server | PlanetScale MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 74 | 63 | ClickHouse MCP Server +11 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 82 | PlanetScale MCP Server +3 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 74 | PlanetScale MCP Server +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 66 | 77 | PlanetScale MCP Server +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 15 | ClickHouse MCP Server +45 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 94 | 80 | ClickHouse MCP Server +14 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 82 | 70 | ClickHouse MCP Server +12 |\n| Negative events | ≤15 | -8 | 0 | |\n| **Total** | | **64.6 · B** | **66.4 · B** | |\n\n## Facts side by side\n\n| Fact | ClickHouse MCP Server | PlanetScale MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | ClickHouse | PlanetScale |\n| Hosted endpoint | no (local only) | `https://mcp.pscale.dev/mcp/planetscale` |\n| Transports | stdio, Streamable HTTP, SSE (legacy) | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Free | Paid |\n| x402 | no | no |\n| Licence | Apache-2.0 | Proprietary hosted service under PlanetScale's Terms of Service. The 13 tools in planetscale/mcp-server are Apache-2.0 |\n| Tools exposed | 3 | 25 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.ClickHouse/mcp-clickhouse` | `io.github.planetscale/mcp-server` |\n| Last release | 2026-09-21 | 2026-10-08 |\n| Terms last updated | no document linked | no date given |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | not found in the text |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | not found in the text |\n| Popularity | 883 stars, 47k PyPI/wk | none |\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**PlanetScale MCP Server.** OAuth scopes set no, read-only or full database access per organisation or database, each query runs on a credential created and deleted for that call, and an insights-only endpoint drops both SQL tools. Destructive statements are gated by a flag the model sets itself, no rate limit was found, and every plan needs a card.\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### PlanetScale MCP Server\n\n1. Use `https://mcp.pscale.dev/mcp/planetscale-insights-only` when the task needs no SQL. It omits both query tools\n2. Pass `organization`, `database` and `branch` on every query call. Record them in `AGENTS.md` to skip the listing calls\n3. Show the person the exact DELETE or DDL statement and get approval before setting `confirm_destructive: true`\n4. Keep queries under 50 seconds and add your own `LIMIT`. The query tools cancel at 50 seconds and return every row\n5. For a service token send `Authorization: Bearer pscale_tkn_...` with the secret only. The `id:secret` form is rejected\n\n## Questions\n\n### Which is better for AI agents, ClickHouse MCP Server or PlanetScale MCP Server?\n\nPlanetScale MCP Server scores 66.4 (B) on agent readiness against ClickHouse MCP Server's 64.6 (B), and leads in 3 of 7 scored categories. ClickHouse MCP Server leads on reliability, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do ClickHouse MCP Server and PlanetScale MCP Server need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call ClickHouse MCP Server and PlanetScale MCP Server without installing anything?\n\nClickHouse MCP Server runs on your own machine, with no hosted endpoint listed. PlanetScale MCP Server has a hosted endpoint at https://mcp.pscale.dev/mcp/planetscale.\n\n### Are ClickHouse MCP Server and PlanetScale MCP Server open source?\n\nClickHouse MCP Server is open source (Apache-2.0). No open-source release is listed for PlanetScale MCP Server.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clickhouse-mcp-server\", \"b\": \"planetscale-mcp\"}`. From a terminal: `anchor compare clickhouse-mcp-server planetscale-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/planetscale-mcp.json\n\n## Other comparisons with ClickHouse MCP Server or PlanetScale MCP Server\n\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- [PlanetScale MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-mcp-pro.md)\n- [PlanetScale MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived.md)\n- [PlanetScale MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed.md)\n- [PlanetScale MCP Server vs Supabase API + MCP](https://www.anchorterminal.com/compare/planetscale-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 PlanetScale MCP Server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-planetscale-mcp.md)\n- [PlanetScale MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "ClickHouse MCP Server vs PlanetScale MCP Server", "url": "" } ], "description": "PlanetScale scores 66.4 (B) to ClickHouse's 64.6 (B) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ClickHouse MCP Server B 64.6", "PlanetScale MCP Server B 66.4", "scores" ], "h1": "ClickHouse MCP Server vs PlanetScale MCP Server", "image": "https://www.anchorterminal.com/assets/og/compare-clickhouse-mcp-server-vs-planetscale-mcp.png", "path": "/compare/clickhouse-mcp-server-vs-planetscale-mcp", "published": "2026-10-01", "section": "tools", "title": "ClickHouse vs PlanetScale for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp" }, "tokens": { "markdown": 2550, "slim": 830 }, "version": 1 }