# ClickHouse MCP Server > 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. - Canonical: https://www.anchorterminal.com/tools/clickhouse-mcp-server - Markdown: https://www.anchorterminal.com/tools/clickhouse-mcp-server.md (~7,800 tokens) - Slim: https://www.anchorterminal.com/tools/clickhouse-mcp-server.min.md (~1,730 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/clickhouse-mcp-server.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 ## Overview **Grade B · 64.6/100 · rank #312 of 842 · #5 in Databases & files · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | ClickHouse (https://clickhouse.com) | | Kind | MCP server | | Category | Databases & files (https://www.anchorterminal.com/categories/data) | | Transport | stdio, Streamable HTTP, SSE (legacy) | | Auth | OAuth or key · 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 (Free · OSS) · 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). | | x402 | No · No x402, MPP or L402 in the README, the changelog or the source (checked 2026-10-09). | | Licence | Apache-2.0 | | Tools exposed | 3 | | Packages | pypi: `mcp-clickhouse`; oci: `ghcr.io/clickhouse/mcp-clickhouse` | | MCP registry name | `io.github.ClickHouse/mcp-clickhouse` | | Source | https://github.com/ClickHouse/mcp-clickhouse | | Docs | https://github.com/ClickHouse/mcp-clickhouse#readme | | llms.txt | https://clickhouse.com/docs/llms.txt | | Last release | 2026-09-21 | | GitHub stars | 883 (as of 2026-10-09) | | PyPI downloads / week | 47,206 | | What is graded | The open-source server in ClickHouse/mcp-clickhouse, version 0.7.0, which the owner runs. ClickHouse Cloud's hosted Remote MCP server at `https://mcp.clickhouse.cloud/mcp` is a separate product with 13 read-only tools and is not graded here | | Install | `python3 -m pip install mcp-clickhouse` or `uv run --with mcp-clickhouse --python 3.12 mcp-clickhouse`. Python 3.10 to 3.14. Docker images at `ghcr.io/clickhouse/mcp-clickhouse` since 0.4.0. chDB needs the extra, `pip install 'mcp-clickhouse[chdb]'` | | Transports | stdio (default), streamable HTTP (`CLICKHOUSE_MCP_SERVER_TRANSPORT=http`, endpoint `/mcp` on `127.0.0.1:8000`) and SSE, which is deprecated and logs a warning. `/health` is unauthenticated on HTTP and SSE | | Tools | `run_query` (`query`, optional `params`), `list_databases` (no inputs), `list_tables` (`database`, optional `like`, `not_like`, `page_token`, `page_size` default 50, `include_detailed_columns`). `run_chdb_select_query` (`query`) when chDB is enabled. Results are JSON-encoded strings | | Credentials | `CLICKHOUSE_HOST`, `CLICKHOUSE_USER` and `CLICKHOUSE_PASSWORD`, or a client certificate with `CLICKHOUSE_CLIENT_CERT` and `CLICKHOUSE_TLS_MODE` (mutual, proxy or strict). Optional `CLICKHOUSE_ROLE`. The connection uses ClickHouse's HTTP interface on 8443 or 8123, not the native protocol | | Restrictions | `readonly=1` by default. `CLICKHOUSE_ALLOW_WRITE_ACCESS=true` for DDL and inserts, plus `CLICKHOUSE_ALLOW_DROP=true` for destructive statements. With write access on and drop off, the server reads `SHOW GRANTS` once and logs a warning if the user holds destructive privileges | | HTTP protections | Authentication required by default. `CLICKHOUSE_MCP_ALLOWED_HOSTS` and `CLICKHOUSE_MCP_ALLOWED_ORIGINS` validate Host (421 on mismatch) and Origin (403). A wildcard bind refuses to start without an allowed-hosts list. `CLICKHOUSE_MCP_TRUSTED_PROXIES` for `X-Forwarded-Host` | | Limits | `CLICKHOUSE_MCP_QUERY_TIMEOUT` 30 seconds by default, after which the server attempts `KILL QUERY`. `CLICKHOUSE_MCP_MAX_WORKERS` 10. No row or byte limit on `run_query` results | | Usage statistics | No telemetry code was found in the 0.7.0 source. The server sends the client name `mcp_clickhouse` to the ClickHouse it connects to and logs each query's SQL text at INFO level | | Releases | 0.1.0 on 24 December 2024. 0.3.0 on 14 April 2026 (write mode, tool renamed to `run_query`), 0.4.0 on 3 June, 0.4.1 on 17 July, 0.5.0 on 1 September, 0.6.0 on 3 September (FastMCP 4), 0.7.0 tagged 21 September 2026 | | Capabilities | db.sql | | Tags | official, local, open-source, self-hosted, mcp, python, docker, read-only-mode, database | | JSON | https://www.anchorterminal.com/api/v1/tools/clickhouse-mcp-server.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 74 | 14.8 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 79 | 12.8 | | Agent ergonomics | 13% | 16.2 | 65 | 10.6 | | Security & auth | 14% | 17.5 | 66 | 11.6 | | Payments & pricing | 10% | 12.5 | 60 | 7.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 94 | 8.2 | | Transparency & trust (editorial 76, provenance 87) | 7% | 8.8 | 82 | 7.2 | | Negative events | up to −15 | up to −15 | -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). | -8 | | **Total** | | | | **64.6 → B** | ### Why each score - Reliability 74: Scored as local software, since the owner runs it over stdio or its own HTTP listener. Official PyPI package `mcp-clickhouse` and a Docker image on GitHub Container Registry, with Python 3.10 to 3.14 stated (20). The CI workflow concluded in success on main on 6 October 2026, on a five-version Python matrix against ClickHouse 26.3, and the repository holds 403 test functions (25). Three open issues and five open pull requests. Issue #223 on unbounded `run_query` results has been open since 23 August 2026 with no reply, and #155 on per-user access has ten comments (20 of 25). A changelog with a labelled breaking change in 0.5.0 and Compatibility sections in 0.6.0 and 0.7.0, but the changelog file dates only from 14 April 2026, 0.3.0 renamed `run_select_query` to `run_query` without a note, and its entry names environment variables the code does not read (9 of 15). Version 0.7.0, with no stability declaration found (0). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 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). - Agent ergonomics 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). - Security & auth 66: The server holds one ClickHouse user and password, or an X.509 client certificate since 0.7.0, which ClickHouse grants and roles can scope and an admin can revoke. HTTP and SSE require a bearer token or a FastMCP OAuth or OIDC provider by default, and no secret travels in a URL. Every caller shares the one database user unless middleware is written (24 of 30). Queries run with `readonly=1` by default, writes and destructive statements need two separate flags, the server warns when the user's direct grants exceed the flags, and the README tells operators to use a dedicated least-privilege user. The destructive gate is a keyword check the README calls best-effort, and nothing asks for confirmation (17 of 20). Query results reach the model as stored. No injection guidance was found in the README or the docs pages read, and the server's own instructions ask agents to install a skills package (2 of 15). Each query's SQL is logged at INFO, ClickHouse's `system.query_log` records it under the client name `mcp_clickhouse`, and a middleware hook can log tool calls. No per-caller identity reaches ClickHouse (9 of 15). ClickHouse has a valid security.txt, a Bugcrowd bounty programme, and SOC 2 Type 2 and ISO 27001 on its trust centre. This repository has no SECURITY.md and no published advisories, though 0.3.0 and 0.5.0 carried security fixes (14 of 20). - Payments & pricing 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 feature and is not what this listing grades. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 94: v0.7.0 was tagged and released on GitHub on 21 September 2026, 18 days before the check (30). Four tagged releases in the 90 days before the check, 0.4.1 on 17 July, 0.5.0 on 1 September, 0.6.0 on 3 September and 0.7.0 (20). Three open issues against a dozen closed between July and October 2026, most with a maintainer reply and a fix version. Issue #223 has had no reply in six weeks and pull request #184 has been open since May (20 of 25). Listed in the official MCP registry as `io.github.ClickHouse/mcp-clickhouse`, a GitHub-verified namespace, with 0.7.0 published on 21 September 2026 and marked latest (15). Dependabot updates merged on 1 October 2026, a lock file, and a CI matrix that tests the minimum supported driver. `server.json` on main still says 0.6.0 (9 of 10). - Transparency & trust 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). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (20 items): https://www.anchorterminal.com/fixes/clickhouse-mcp-server.md (JSON https://www.anchorterminal.com/fixes/clickhouse-mcp-server.json) ### What we couldn't check - The lead said no hosted server was shown. ClickHouse Cloud has a hosted Remote MCP server at https://mcp.clickhouse.cloud/mcp with OAuth 2.0 or a Cloud API key and 13 read-only tools. It is a separate Cloud feature and this listing grades the open-source server only - unchecked: the PyPI project page, which answered with a JavaScript client challenge, and the PyPI JSON API, which robots.txt disallows. The 0.7.0 release date rests on the git tag, the GitHub release and the MCP registry entry, all 21 September 2026. The changelog heading says 18 September - unchecked: tool definitions as a client receives them from `tools/list`. We did not run the server, so input schemas and the absence of annotations are read from the source - unchecked: the claim in issue #131 that DDL ran under `readonly=1` and that a production table was dropped. It is the reporter's account and no maintainer confirmed or disputed it in the thread - unchecked: ClickHouse Cloud pricing and its trial, which matter only when the server points at ClickHouse Cloud - unchecked: the Bugcrowd programme page and whether mcp-clickhouse is in scope - unchecked: the GitHub Container Registry image page, which rests on the changelog and `server.json` - No privacy document addresses this software, so `provenance.privacy` and `provenance.terms` are both left out - The server's MCP instructions tell agents to run `npx -y skills add clickhouse/agent-skills --all`. Recorded as a fact with no deduction, and not acted on ### Sources - README, tools, authentication, write gates and environment variables: (seen 2026-10-09) - changelog, 0.1.0 to 0.7.0: (seen 2026-10-09) - tool registration and descriptions, read from a clone of main at d21fe75 (7 October 2026): (seen 2026-10-09) - server instructions addressed to agents: (seen 2026-10-09) - package metadata, dependencies and supported Python versions: (seen 2026-10-09) - CI workflow definition: (seen 2026-10-09) - workflow runs on main: (seen 2026-10-09) - repository statistics: (seen 2026-10-09) - open and closed issues and pull requests: (seen 2026-10-09) - issue #223, unbounded run_query results: (seen 2026-10-09) - issue #131, DDL through run_select_query: (seen 2026-10-09) - issue #188, FastMCP advisories flagged by scanners, closed as fixed in 0.6.0: (seen 2026-10-09) - GitHub release notes, v0.1.13 to v0.7.0: (seen 2026-10-09) - repository security advisories (none): (seen 2026-10-09) - MCP registry search: (seen 2026-10-09) - PyPI weekly downloads: (seen 2026-10-09) - ClickHouse docs page on the open-source MCP server: (seen 2026-10-09) - Remote MCP in Cloud, with the comparison table: (seen 2026-10-09) - llms.txt: (seen 2026-10-09) - docs llms.txt: (seen 2026-10-09) - robots.txt, with Content-Signal ai-input=yes: (seen 2026-10-09) - security.txt: (seen 2026-10-09) - ClickHouse security policy and Bugcrowd programme: (seen 2026-10-09) - trust centre, compliance list: (seen 2026-10-09) - privacy policy: (seen 2026-10-09) - domain registration: (seen 2026-10-09) ## Who's behind it (provenance 87/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | ClickHouse, Inc. | 20/20 | | Domain age | clickhouse.com, registered 1999-03-12 (27 years) | 15/15 | | Endpoint on the vendor's domain | no hosted endpoint | n/a | | Terms of service | nothing hosted, so the Apache-2.0 licence stands in | 10/10 | | Privacy policy | nothing hosted, not scored | n/a | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service**. Nothing is hosted by the vendor, so there are no terms of service to read. The Apache-2.0 licence stands in and the check scores in full. **Privacy policy**. Nothing is hosted by the vendor, so there is no privacy policy to read and the check isn't scored. ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## 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 ## Before you call it (notes for agents) 1. Put a `LIMIT` on every `run_query` call. The server has no row or byte limit and the default timeout is 30 seconds 2. Call the tool `run_query`. ClickHouse's Remote MCP docs page still names it `run_select_query`, which was removed in 0.3.0 3. Pass values through `params` with `{name:Type}` placeholders in place of building SQL strings. Tuple and Map types can't be bound 4. Set `include_detailed_columns` to false on `list_tables` for wide schemas. Page tokens are single-use and expire after one hour 5. Connect with a dedicated ClickHouse user holding only the grants needed, and point `CLICKHOUSE_PORT` at the HTTP interface (8123 or 8443), not 9000 ## Connect Install: ```bash python3 -m pip install mcp-clickhouse ``` MCP client configuration: ```json { "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" } } } } ``` Through letme (picks today, calling later): https://letme.dev/clickhouse-mcp-server. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Supabase API + MCP | BB | 75.6 | 44 | db.sql | no | https://www.anchorterminal.com/tools/supabase-mcp.md | | Render MCP Server | B | 63.6 | 352 | db.sql | no | https://www.anchorterminal.com/tools/render-mcp-server.md | | Atlan | B | 62.5 | 385 | db.sql | no | https://www.anchorterminal.com/tools/atlan.md | | Alation | C | 60.3 | 472 | db.sql | no | https://www.anchorterminal.com/tools/alation.md | | Postgres MCP Pro | F | 36.7 | 821 | db.sql | no | https://www.anchorterminal.com/tools/postgres-mcp-pro.md | | PostgreSQL (archived MCP reference server) | F | 18.4 | 838 | db.sql | no | https://www.anchorterminal.com/tools/postgres-reference-server-archived.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Three tools by default, `run_query`, `list_databases` and `list_tables`, plus `run_chdb_select_query` and one prompt when `CHDB_ENABLED=true` and the `chdb` extra is installed (source: ) - Queries run with ClickHouse's `readonly=1` setting by default. `CLICKHOUSE_ALLOW_WRITE_ACCESS=true` allows DDL and inserts, and `CLICKHOUSE_ALLOW_DROP=true` is needed as well for DROP, TRUNCATE, DELETE, UPDATE and similar. The README calls the second gate a best-effort accident guard, not a security boundary (source: ) - 0.7.0 added a `params` object on `run_query` for ClickHouse `{name:Type}` placeholders, and the description points to `DESCRIBE ()` and `EXPLAIN ESTIMATE ` as optional checks before a query runs (source: ) - `run_query` has no limit on result size. Issue #223 of 23 August 2026 reports 3 million rows and a 231 MiB payload from one `SELECT *` inside the 30-second default timeout, and pull request #224 to bound it is open (source: ) - 0.5.0 on 1 September 2026 added Host and Origin validation on HTTP and SSE as a labelled breaking change, closed a `fastmcp run` launch path that served without authentication, and widened the destructive gate to statements that had run with write access alone (source: ) - 0.6.0 moved to FastMCP 4 and the README says the server implements MCP `2026-07-28` with legacy handshakes from `2024-11-05` to `2025-11-25`. The standalone SSE transport is deprecated with no removal date (source: ) - The server's MCP instructions tell agents to consider ClickHouse's Agent Skills and give an `npx -y skills add clickhouse/agent-skills --all` command. We record this as a fact and did not act on it (source: ) - ClickHouse Cloud has a separate hosted Remote MCP server at `https://mcp.clickhouse.cloud/mcp` with OAuth 2.0 or a Cloud API key and 13 read-only tools, for Cloud services only (source: ) ## Compare - [ClickHouse MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-mcp-pro.md): B 64.6 vs F 36.7 - [ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.md): B 64.6 vs F 18.4 - [ClickHouse MCP Server vs Supabase API + MCP](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-supabase-mcp.md): B 64.6 vs BB 75.6 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on clickhouse.com or one of its subdomains, or the README of github.com/ClickHouse/mcp-clickhouse. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "clickhouse-mcp-server", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html ClickHouse MCP Server on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![ClickHouse MCP Server on Anchor Terminal](https://www.anchorterminal.com/badges/clickhouse-mcp-server.svg)](https://www.anchorterminal.com/tools/clickhouse-mcp-server) ``` Plain link: ```html ClickHouse MCP Server on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say ClickHouse MCP Server is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/clickhouse-mcp-server-dark.png - Light: https://www.anchorterminal.com/assets/share/clickhouse-mcp-server-light.png