clickhouse-mcp-server
Related Servers
Alternatives to clickhouse-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMinimal MCP server for read-only access to ClickHouse, enabling AI agents to explore schemas and execute SELECT queries safely.-
- AlicenseAqualityBmaintenanceA read-only MCP server for ClickHouse that enables metadata discovery, parameterized SELECT queries, SHOW introspection, query analysis, and snapshot mode for large result sets, with profile-based configuration and strict no-DML/DDL enforcement.8MIT
- AlicenseAqualityCmaintenanceA read-only MCP server for ClickHouse that enables AI agents to discover schema, sample data, and run read-only SQL queries to investigate observability data like logs, metrics, and traces.616MIT
- AlicenseBqualityFmaintenanceAn MCP server implementation that enables Claude AI to interact with Clickhouse databases. Features include secure database connections, query execution, read-only mode support, and multi-query capabilities.22MIT
- Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server for executing SQL queries on PostgreSQL and ClickHouse with per-connection allow/deny policies by statement group.-
TDQS
Scored across 4 tools
Each tool has a unique and clearly defined purpose. There is no overlap; an agent can easily distinguish between describing a table, listing databases, listing tables, and running arbitrary queries.
All tool names follow a consistent verb_noun pattern (describe, list, list, run). The naming is predictable and intuitive.
With four tools, the server is well-scoped for its read-only metadata and querying purpose. Each tool is essential and provides a distinct function without unnecessary bloat.
The tool set covers the core operations for inspecting a ClickHouse server's schema and executing queries. While some advanced metadata operations (e.g., listing table engines) are missing, the generic run_select_query tool can compensate for many gaps, making the surface reasonably complete.