mcp-clickhouse
Related Servers
Alternatives to mcp-clickhouse
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables interaction with ClickHouse databases via MCP, providing tools to list databases and tables and execute safe SELECT, SHOW, and DESCRIBE queries.30MIT
- FlicenseAqualityCmaintenanceRead-only MCP server for ClickHouse that allows listing databases and tables, describing schemas, and running SELECT queries.4-
- FlicenseNot gradedqualityCmaintenanceMCP server for executing SQL queries on PostgreSQL and ClickHouse with per-connection allow/deny policies by statement group.-
- 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
- AlicenseCqualityCmaintenanceEnables connecting to multiple ClickHouse instances via dynamic registration or YAML configuration, supporting SQL queries and data source management through MCP tools.6Apache 2.0
- 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
TDQS
Scored across 9 tools
Most tools target clearly distinct resources, but describe_table/show_create_table and list_tables/table_stats have some overlapping schema and size information. Descriptions are detailed enough that an agent can usually pick correctly.
Names are mostly lowercase with underscores, but conventions vary: list_* and show_* use verb_noun, while running_queries, table_stats, server_metrics, and cluster_info are noun phrases, and query is a bare verb. The set is readable but not pattern-consistent.
Nine tools is a well-scoped size for a ClickHouse observability/read server. Each tool covers a meaningful slice of database introspection and querying without feeling bloated.
The query tool explicitly says non-read statements should use execute in read-write mode, but no execute tool exists in the set. This is a significant dead end: agents are directed to a missing tool, and write/DDL operations are entirely unsupported despite being referenced.