About clickhouse-dataops-mcp
clickhouse-dataops-mcp is a read-only ClickHouse MCP server for DataOps teams, combining query execution with optimization advice, pipeline latency analysis, and data-quality checks. It adds diagnostics and safety controls beyond basic query access.
Key features
- 01Run SELECT with partition warnings
- 02Analyze queries with EXPLAIN
- 03Inspect schemas and table catalog
- 04Measure CDC pipeline latency
- 05Detect data quality issues
- 06Diagnose slow queries and disk usage
Use cases
- 01Review query plans and optimization options
- 02Monitor CDC segment latency
- 03Check tables for nulls, duplicates, and gaps
- 04Investigate slow queries and storage use
MCP support
Exposes ClickHouse query and DataOps diagnostic tools to MCP clients. Queries are read-only, with DDL and DML blocked, as well as multi-statement input.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
uvx clickhouse-dataops-mcpCLICKHOUSE_HOSTClickHouse HTTP hostCLICKHOUSE_PORTClickHouse HTTP portCLICKHOUSE_PASSWORDSecretClickHouse passwordLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEclickhouse-dataops-mcp
mcp-name: io.github.Aguantar/clickhouse-dataops-mcp
A DataOps-focused MCP server for ClickHouse with query optimization, pipeline latency analysis, and data quality monitoring.
Features
Unlike generic ClickHouse MCP servers that only run queries, this server acts as a query optimization advisor:
ch_query— Execute SELECT with automatic partition pruning warningsch_explain_query— EXPLAIN-based analysis with optimization suggestionsch_table_schema— Comprehensive table metadata (columns, keys, partitions, samples)ch_pipeline_latency— CDC pipeline per-segment latency (p50/p95/p99)ch_data_quality— Null/duplicate/gap detection with market coverage checksch_slow_queries— Slow query detection with root cause diagnosisch_disk_usage— Disk analysis with TTL and optimization recommendationsch_list_tables— Table catalog with built-in descriptions
Safety
All queries are read-only. DDL/DML operations are blocked at the SQL validation layer:
- Blocked:
DROP,TRUNCATE,DELETE,ALTER,INSERT,UPDATE,CREATE, etc. - Multi-statement queries blocked (
;separator) - Comment-based bypass prevented (comments stripped before validation)
- System tables restricted to allowlist
- Query timeout: 30 seconds
- Row limit enforcement
Installation
pip install clickhouse-dataops-mcp
Usage with Claude Code
Add to your .mcp.json:
{
"mcpServers": {
"clickhouse": {
"command": "clickhouse-mcp-server",
"env": {
"CLICKHOUSE_HOST": "localhost",
"CLICKHOUSE_PORT": "8123",
"CLICKHOUSE_DATABASE": "cdc_pipeline"
}
}
}
}
Environment Variables
| Variable | Default | Description |
|---|---|---|
CLICKHOUSE_HOST | localhost | ClickHouse HTTP host |
CLICKHOUSE_PORT | 8123 | ClickHouse HTTP port |
CLICKHOUSE_USER | default | ClickHouse username |
CLICKHOUSE_PASSWORD | (empty) | ClickHouse password |
CLICKHOUSE_DATABASE | cdc_pipeline | Default database |
CLICKHOUSE_QUERY_TIMEOUT | 30 | Query timeout in seconds |
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.