| FMRS | 64 / 100 · C | 79 / 100 · B | 74 / 100 · B |
|---|
| Reliability | 7 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 14 / 20 | 18 / 20 | 13 / 20 |
|---|
| Maintenance | 15 / 20 | 17 / 20 | 17 / 20 |
|---|
| Documentation | 14 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 15 / 20 |
|---|
| Best for | - Teams needing real-time monitoring and AI-driven optimization advice for ClickHouse
- Developers and data engineers who want to surface ClickHouse data to AI assistants
- Users deploying on Docker, Kubernetes, or ClickHouse Cloud
| - Teams already using ClickHouse who want AI assistants to access data directly.
- Scenarios requiring fast, read-only data queries and schema exploration.
| - Teams that want precise control over which database operations an AI can perform, rather than open arbitrary SQL execution
- Scenarios needing a unified MCP setup across multiple database engines
|
|---|
| Not for | - Users who don't need ClickHouse monitoring or optimization suggestions
- Those seeking automatic schema changes or DDL execution (chmonitor recommends only)
- Scenarios requiring write or modification access to ClickHouse data
| - Scenarios requiring write access to the database without explicit opt-in.
- Production environments with stringent security requirements that avoid default permission settings.
| - Lightweight cases that just want to run a few ad-hoc SQL queries without maintaining a tools.yaml config (a simpler single-database MCP may be a better fit)
|
|---|
| Required permissions | - Read-only access to ClickHouse system.* tables (schema, queries, merges, replication, etc.)
- Requires a ClickHouse user with read permissions on system tables (e.g., default or a dedicated read-only user)
- For hosted instance, a valid API key is required
| - Requires read-only access to ClickHouse database (default).
- Optional: write access via CLICKHOUSE_ALLOW_WRITE_ACCESS.
- Optional: destructive operations via CLICKHOUSE_ALLOW_DROP.
| - Database credentials (username/password/connection string) are supplied via env vars or config
- A tool's actual permission is whatever SQL statement is defined in tools.yaml — designed for least privilege, but misconfiguration can still over-expose access
|
|---|
| Risks and side effects | - Read-only operations, but ensure API key security to prevent unauthorized access
- AI recommendations may be inaccurate; review before applying
- When self-hosting, protect ClickHouse credentials (CLICKHOUSE_PASSWORD)
| - If write access is enabled, AI might make unintended modifications.
- If DROP access is enabled, data deletion could occur accidentally.
- Credentials may be exposed via environment variables.
| - If tools.yaml defines SQL statements that allow unconstrained writes or deletes, the AI could accidentally modify data
- The prebuilt toolsets (--prebuilt) favor convenience and may expose broader query capability than a specific business actually needs — use a custom tools.yaml in production
|
|---|
| Supported clients | Claude Desktop, Claude Code, Cursor | Claude Desktop | Claude Code, Gemini CLI, Zed, Antigravity |
|---|
| Tools | 0 | 4 | 0 |
|---|