# ClickHouse MCP Server vs Redis MCP

> ClickHouse scores 64.6 (B) to Redis MCP's 55.7 (C) for databases. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp
- Markdown: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp.min.md (~530 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp.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 Redis MCP's 55.7 (C), and leads in 6 of 7 scored categories. Both do 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
- Redis MCP: grade C, 55.7/100, rank #652 of 950. Markdown https://www.anchorterminal.com/tools/redis-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/redis-mcp.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 62
- Schema & documentation, 79 against 64
- Agent ergonomics, 65 against 39
- Security & auth, 66 against 54
- Maintenance & community, 94 against 57
- Transparency & trust, 82 against 76

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 *`

### Redis MCP (C)

Good for: Teams with a Redis database that want an agent to read and write keys, streams, JSON documents and vector indexes on a developer's machine.

Watch for: 53 tools load at once, with no toolsets and no read-only subset. Pull request #161 for a tool allowlist has been open since 28 July 2026


## Score by category

| Category | Weight | ClickHouse MCP Server | Redis MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 74 | 62 | ClickHouse MCP Server +12 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 64 | ClickHouse MCP Server +15 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 39 | ClickHouse MCP Server +26 |
| Security & auth | 14% (17.5 this run) | 66 | 54 | ClickHouse MCP Server +12 |
| Payments & pricing | 10% (12.5 this run) | 60 | 60 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 94 | 57 | ClickHouse MCP Server +37 |
| Transparency & trust | 7% (8.8 this run) | 82 | 76 | ClickHouse MCP Server +6 |
| Negative events | ≤15 | -8 | -2 | |
| **Total** | | **64.6 · B** | **55.7 · C** | |

## Facts side by side

| Fact | ClickHouse MCP Server | Redis MCP |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | ClickHouse | Redis |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio, Streamable HTTP, SSE (legacy) | stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 3 | 53 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| MCP registry | `io.github.ClickHouse/mcp-clickhouse` | `io.github.redis/mcp-redis` |
| Last release | 2026-09-21 | 2026-08-04 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Customer content may train models |  |  |
| Terms restrict automated access |  |  |
| Terms restrict benchmarking |  |  |
| Terms or service can change without notice |  |  |
| Arbitration or class-action waiver |  |  |
| Popularity | 883 stars, 47k PyPI/wk | 633 stars, 3.6k PyPI/wk |

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

**Redis MCP.** Redis's server, under the MIT licence, maps 53 tools onto Redis commands, with typed inputs and a nightly CI run that passed on 9 October 2026. It has no read-only mode, no tool annotations and no changelog file, release 0.5.1 changed the `unsubscribe` input without a note, and PyPI installs failed to start from 28 July to 5 August 2026.

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

### Redis MCP

1. Pass the connection with `--url` or explicit flags. The `redis-mcp-server` command overrides `REDIS_HOST`, `REDIS_PORT`, `REDIS_DB`, `REDIS_SSL` and `REDIS_CLUSTER_MODE` with its own defaults when flags are absent
2. Use `scan_keys` with the returned cursor until it is 0. `scan_all_keys`, `hgetall`, `smembers` and `json_get` return everything they match with no limit
3. Read failures from the text. Tools return strings such as `Error ...` or an `error` key in place of an MCP error result
4. Keep the `subscription_id` from `subscribe` or `psubscribe` and pass it to `read_messages` and `unsubscribe`. Idle subscriptions close after 300 seconds
5. Connect as a Redis ACL user limited to the keys and command categories needed, since the server has no read-only switch and `delete` runs without confirmation

## Questions

### Which is better for AI agents, ClickHouse MCP Server or Redis MCP?

ClickHouse MCP Server scores 64.6 (B) on agent readiness against Redis MCP's 55.7 (C), and leads in 6 of 7 scored categories.

### Do ClickHouse MCP Server and Redis MCP need an API key?

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

### Can an agent call ClickHouse MCP Server and Redis MCP without installing anything?

ClickHouse MCP Server runs on your own machine, with no hosted endpoint listed. Redis MCP runs on your own machine, with no hosted endpoint listed.

### Are ClickHouse MCP Server and Redis MCP open source?

Yes. ClickHouse MCP Server is open source (Apache-2.0). Redis MCP is open source (MIT).


## For agents

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

## Other comparisons with ClickHouse MCP Server or Redis MCP

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