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
C
ChMonitor
Community
AI operational advisor for ClickHouse with MCP server
GitHub source repository ↗
64FMRS · C
chmonitor is a MCP server for ClickHouse providing read-only monitoring and AI recommendations, suitable for teams integrating ClickHouse with AI tools. It supports multiple deployment methods, has active community and documentation, but note it recommends rather than auto-executes, requiring user evaluation.
chmonitor is an open-source operational advisor for ClickHouse, providing real-time monitoring and AI-driven recommendations for indexes, partitions, and materialized views. It acts as a read-only MCP server exposing schema, queries, merges, replication, and cluster health over HTTP streamable transport, self-hostable or via cloud.
Tools
The tool list has not been reviewed yet.
Setup
- Ensure you have a ClickHouse cluster and a chm_ API key (create via dashboard 'Operate/Authentication/API Keys').
- Configure your MCP client (e.g., Claude Desktop, Claude Code, Cursor) with server URL
https://dash.chmonitor.dev/api/mcpand headerAuthorization: Bearer chm_YOUR_API_KEY. - Alternatively, a self-hosted instance can run without authentication, omitting the Authorization header.
claude_desktop_config.json
{
"mcpServers": {
"chmonitor": {
"url": "https://dash.chmonitor.dev/api/mcp",
"headers": {
"Authorization": "Bearer chm_YOUR_API_KEY"
}
}
}
}
Fit and risk
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
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
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)
Troubleshooting
- Verify API key is valid and not revoked
- Confirm ClickHouse instance is reachable and network firewalls are not blocking
- For self-hosted, check correct CLICKHOUSE_* environment variables are set
- Inspect MCP server logs for authentication and connection errors
Use cases
Monitor ClickHouse cluster health, queries, merges, and replication
Get AI-powered recommendations for schema and performance optimizations (read-only, no DDL execution)
Integrate ClickHouse with AI tools like Claude or Cursor for natural language querying
Supported clients
Claude DesktopFull support
Claude CodeFull support
CursorFull support