Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"clickhouse": {
"env": {
"CLICKHOUSE_HOST": "localhost",
"CLICKHOUSE_PORT": "8123",
"CLICKHOUSE_DATABASE": "cdc_pipeline"
},
"command": "clickhouse-mcp-server"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
mcp-name: io.github.Aguantar/clickhouse-dataops-mcp
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'clickhouse-dataops-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked clickhouse-dataops-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in data / devops
Query and manage PostgreSQL databases directly from AI assistants
MCP server for using the GitLab API
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
Manage Supabase projects — databases, auth, storage, and edge functions
MCP Security Weekly
Get CVE alerts and security updates for io.github.Aguantar/clickhouse-dataops-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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