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

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.

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

CategoryWeight this runClickHouse MCP ServerRedis MCPEdge
Reliability16%207462ClickHouse MCP Server +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27964ClickHouse MCP Server +15
Agent ergonomics13%16.26539ClickHouse MCP Server +26
Security & auth14%17.56654ClickHouse MCP Server +12
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89457ClickHouse MCP Server +37
Transparency & trust7%8.88276ClickHouse MCP Server +6
Negative events≤15-8-2
Total64.6 · B55.7 · C

Facts side by side

FactClickHouse MCP ServerRedis MCP
KindMCP serverMCP server
VendorClickHouseRedis
Hosted endpointno (local only)no (local only)
Transportsstdio, Streamable HTTP, SSE (legacy)stdio
AuthOAuth or keyOAuth or key
PricingFreeFree
x402nono
LicenceApache-2.0MIT
Tools exposed353
Read-only variant documentedyesyes
llms.txtyesyes
MCP registryio.github.ClickHouse/mcp-clickhouseio.github.redis/mcp-redis
Last release2026-09-212026-08-04
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno 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
Popularity883 stars, 47k PyPI/wk633 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).

Other comparisons with ClickHouse MCP Server or Redis MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.