Qdrant MCP vs ClickHouse MCP
Both are databases & vector stores MCP servers, and we ran both through the same test (file query, roundtrip) in each app. Qdrant MCP passed 4 of 4 apps we tested it in; ClickHouse MCP passed 3 of 3.
Test results side by side
| Qdrant MCP | ClickHouse MCP | |
|---|---|---|
| Claude Code | Passed 2026-10-20 | Passed 2026-10-23 |
| Cursor | Passed 2026-10-20 | Passed 2026-10-23 |
| Claude Desktop | Passed 2026-10-19 | Not tested yet |
| ChatGPT (Codex) | Passed 2026-10-20 | Passed 2026-10-23 |
| Tools exposed (protocol check) | 2 tools | 1 tools |
| GitHub stars | 1,549 | 889 |
| License | Apache-2.0 | Apache-2.0 |
| Last push | 2026-09-04 | 2026-10-15 |
Results from our own harness runs, dated per cell. Stars and last push from GitHub at our last data refresh. We don’t pick a winner here: which one fits depends on your app and setup.
What each does
Qdrant MCP: Qdrant's official server: store and semantically search memories in a Qdrant collection, locally or on Qdrant Cloud.
ClickHouse MCP: ClickHouse's official MCP server: agents can list databases and tables and run SQL queries against your ClickHouse cluster (read-only by default).
