# ClickHouse MCP Server vs Snowflake-managed MCP server

> ClickHouse scores 64.6 (B) to Snowflake-managed's 56.4 (C) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed
- Markdown: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.md (~2,500 tokens)
- Slim: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.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

ClickHouse MCP Server scores 64.6 (B) on agent readiness against Snowflake-managed MCP server's 56.4 (C), and leads in 5 of 7 scored categories. Snowflake-managed MCP server leads on security & auth. Both do sql databases.

- 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
- Snowflake-managed MCP server: grade C, 56.4/100, rank #633 of 950. Markdown https://www.anchorterminal.com/tools/snowflake-managed.md · JSON https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json
- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md
- All 43 databases comparisons: https://www.anchorterminal.com/compare/data/index.md

## Which one, for what

### ClickHouse MCP Server (B)

Good 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.

Ahead on:
- Reliability, 74 against 55
- Schema & documentation, 79 against 61
- Agent ergonomics, 65 against 46
- Payments & pricing, 60 against 35
- Maintenance & community, 94 against 55

Also in its favour:
- Runs on your own machine
- Open source

Watch for: `run_query` returns every row. Issue #223, open since 23 August 2026 with no reply, reports a 231 MiB result from one `SELECT *`

### Snowflake-managed MCP server (C)

Good for: A company that already keeps its data in Snowflake and wants outside MCP clients to query it under existing roles, best through one Cortex Agent tool.

Ahead on:
- Security & auth, 77 against 66

Watch for: No rate limits for the MCP endpoint and no JSON-RPC error codes were found in the reviewed documentation


## Score by category

| Category | Weight | ClickHouse MCP Server | Snowflake-managed MCP server | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 74 | 55 | ClickHouse MCP Server +19 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 61 | ClickHouse MCP Server +18 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 46 | ClickHouse MCP Server +19 |
| Security & auth | 14% (17.5 this run) | 66 | 77 | Snowflake-managed MCP server +11 |
| Payments & pricing | 10% (12.5 this run) | 60 | 35 | ClickHouse MCP Server +25 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 94 | 55 | ClickHouse MCP Server +39 |
| Transparency & trust | 7% (8.8 this run) | 82 | 84 | Snowflake-managed MCP server +2 |
| Negative events | ≤15 | -8 | -2 | |
| **Total** | | **64.6 · B** | **56.4 · C** | |

## Facts side by side

| Fact | ClickHouse MCP Server | Snowflake-managed MCP server |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | ClickHouse | Snowflake Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio, Streamable HTTP, SSE (legacy) | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Free | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | Proprietary service under Snowflake's terms of service |
| Tools exposed | 3 | none |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| MCP registry | `io.github.ClickHouse/mcp-clickhouse` | not listed |
| Last release | 2026-09-21 | 2026-08-20 |
| Terms last updated | no document linked | 2026-04-16 |
| Privacy policy last updated | no document linked | 2026-07-01 |
| Customer content may train models |  | not found in the text |
| Terms restrict automated access |  | not found in the text |
| Terms restrict benchmarking |  | not found in the text |
| Terms or service can change without notice |  | not found in the text |
| Arbitration or class-action waiver |  | yes |
| Popularity | 883 stars, 47k PyPI/wk | none |

## 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.

**Snowflake-managed MCP server.** Tools are governed by Snowflake roles, the SQL tool is read-only by default, and sign-in runs through Snowflake OAuth or a company identity provider. No rate limits or tool-call error codes were found in the reviewed documentation, and a person must create the account, the server object and the OAuth integration before an agent can connect.

## Before you call either

### ClickHouse MCP Server

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

### Snowflake-managed MCP server

1. Send `Accept: application/json, text/event-stream` and read `tools/call` results as an SSE stream that ends with `data: [DONE]`
2. Write the account hostname with hyphens, not underscores, or some clients fail to connect
3. Check the user's `DEFAULT_ROLE` and `DEFAULT_WAREHOUSE` first. Clients that request `session:role:all` get the default role, and a missing warehouse stops the session starting
4. Keep SQL results narrow. Responses over 250 KB are truncated with no paging, and agent tool responses can pass 200 KB
5. Treat `invalid_client` from `/oauth/token-request` as a possible network policy block as well as a wrong credential

## Questions

### Which is better for AI agents, ClickHouse MCP Server or Snowflake-managed MCP server?

ClickHouse MCP Server scores 64.6 (B) on agent readiness against Snowflake-managed MCP server's 56.4 (C), and leads in 5 of 7 scored categories. Snowflake-managed MCP server leads on security & auth.

### Do ClickHouse MCP Server and Snowflake-managed MCP server need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call ClickHouse MCP Server and Snowflake-managed MCP server without installing anything?

ClickHouse MCP Server runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Snowflake-managed MCP server.

### Are ClickHouse MCP Server and Snowflake-managed MCP server open source?

ClickHouse MCP Server is open source (Apache-2.0). No open-source release is listed for Snowflake-managed MCP server.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "clickhouse-mcp-server", "b": "snowflake-managed"}`. From a terminal: `anchor compare clickhouse-mcp-server snowflake-managed`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clickhouse-mcp-server.json and https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json

## Other comparisons with ClickHouse MCP Server or Snowflake-managed MCP server

- [ClickHouse MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.md)
- [ClickHouse MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-mcp-pro.md)
- [ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.md)
- [ClickHouse MCP Server vs Supabase API + MCP](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-supabase-mcp.md)
- [PlanetScale MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed.md)
- [Postgres MCP Pro vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed.md)
- [PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.md)
- [Snowflake-managed MCP server vs Supabase API + MCP](https://www.anchorterminal.com/compare/snowflake-managed-vs-supabase-mcp.md)
- [ClickHouse MCP Server vs MongoDB MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-mongodb-mcp.md)
- [ClickHouse MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp.md)
- [MongoDB MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-snowflake-managed.md)
- [Redis MCP vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.md)