Head to head · Databases · October 2026 research run
ClickHouse MCP Server vs 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. Both do databases.
Best database, file and memory tools for AI agents · All 43 databases comparisons
Which one, for what
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 *
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.
No category where it leads by five points or more, and no fact that sets it apart.
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 this run | ClickHouse MCP Server | Redis MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 74 | 62 | ClickHouse MCP Server +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 79 | 64 | ClickHouse MCP Server +15 |
| Agent ergonomics | 13%16.2 | 65 | 39 | ClickHouse MCP Server +26 |
| Security & auth | 14%17.5 | 66 | 54 | ClickHouse MCP Server +12 |
| Payments & pricing | 10%12.5 | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 94 | 57 | ClickHouse MCP Server +37 |
| Transparency & trust | 7%8.8 | 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
- Put a
LIMITon everyrun_querycall. 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 itrun_select_query, which was removed in 0.3.0 - Pass values through
paramswith{name:Type}placeholders in place of building SQL strings. Tuple and Map types can't be bound - Set
include_detailed_columnsto false onlist_tablesfor 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_PORTat the HTTP interface (8123 or 8443), not 9000
Redis MCP
- Pass the connection with
--urlor explicit flags. Theredis-mcp-servercommand overridesREDIS_HOST,REDIS_PORT,REDIS_DB,REDIS_SSLandREDIS_CLUSTER_MODEwith its own defaults when flags are absent - Use
scan_keyswith the returned cursor until it is 0.scan_all_keys,hgetall,smembersandjson_getreturn everything they match with no limit - Read failures from the text. Tools return strings such as
Error ...or anerrorkey in place of an MCP error result - Keep the
subscription_idfromsubscribeorpsubscribeand pass it toread_messagesandunsubscribe. Idle subscriptions close after 300 seconds - Connect as a Redis ACL user limited to the keys and command categories needed, since the server has no read-only switch and
deleteruns 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).
Other comparisons with ClickHouse MCP Server or Redis MCP
- Redis MCP vs Supabase API + MCP
- ClickHouse MCP Server vs PlanetScale MCP Server
- ClickHouse MCP Server vs Postgres MCP Pro
- ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)
- ClickHouse MCP Server vs Snowflake-managed MCP server
- ClickHouse MCP Server vs Supabase API + MCP
- ClickHouse MCP Server vs MongoDB MCP Server
- PlanetScale MCP Server vs Redis MCP
- Postgres MCP Pro vs Redis MCP
- PostgreSQL (archived MCP reference server) vs Redis MCP
- Redis MCP vs Snowflake-managed MCP server
- MongoDB MCP Server vs Redis MCP
Machine-readable
- This page as Markdown
/compare/clickhouse-mcp-server-vs-redis-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clickhouse-mcp-server.json·/api/v1/tools/redis-mcp.json - From a terminal
anchor compare clickhouse-mcp-server redis-mcp(the CLI) - Over MCP
compare_tools {"a": "clickhouse-mcp-server", "b": "redis-mcp"}at/mcp, no key