DataOps ClickHouse MCP server with query optimization and pipeline monitoring
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.
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 descriptionsAll queries are read-only. DDL/DML operations are blocked at the SQL validation layer:
DROP, TRUNCATE, DELETE, ALTER, INSERT, UPDATE, CREATE, etc.; separator)pip install clickhouse-dataops-mcp
Add to your .mcp.json:
{
"mcpServers": {
"clickhouse": {
"command": "clickhouse-mcp-server",
"env": {
"CLICKHOUSE_HOST": "localhost",
"CLICKHOUSE_PORT": "8123",
"CLICKHOUSE_DATABASE": "cdc_pipeline"
}
}
}
}
| 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 |
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx clickhouse-dataops-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-aguantar-clickhouse-dataops-mcp": {
"command": "uvx",
"args": [
"clickhouse-dataops-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceclickhouse-dataops-mcppypiio.github.Aguantar/clickhouse-dataops-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.