The open-source ClickHouse MCP server (PyPI package `mcp-clickhouse`, repository ClickHouse/mcp-clickhouse) exposes MCP tools such as `run_query`, `list_databases`, and paginated `list_tables` against ClickHouse clusters, defaulting to read-only SQL unless `CLICKHOUSE_ALLOW_WRITE_ACCESS` is enabled. Optional chDB extras add `run_chdb_select_query` for embedded queries over files and URLs. HTTP/SSE transports require authentication via `CLICKHOUSE_MCP_AUTH_TOKEN`, FastMCP OAuth/OIDC providers, or explicit `CLICKHOUSE_MCP_AUTH_DISABLED=true` for local dev; a `/health` endpoint supports orchestrator probes without credentials per README guidance.
Use cases
- Let agents inspect ClickHouse schemas with paginated `list_tables` filters before writing analytics SQL
- Run read-only diagnostics queries during on-call investigations from MCP clients
- Query local or remote datasets through chDB when the optional extra is installed
- Front HTTP/SSE MCP with bearer tokens or Azure/Google OAuth via FastMCP in production
- Monitor server health through the documented `/health` endpoint on HTTP transports
Key features
- Cursor
- Claude Desktop
- VS Code
- Codex
Frequently Asked Questions
- Are writes allowed by default?
- README states queries run read-only unless CLICKHOUSE_ALLOW_WRITE_ACCESS is explicitly enabled.
- Does stdio transport need auth?
- No—authentication is required for HTTP/SSE transports only per security section.
- What is chDB support?
- Install pip install 'mcp-clickhouse[chdb]' to expose run_chdb_select_query for embedded ClickHouse queries.
Related
Related
3 Indexed items
ClickHouse Cloud Remote MCP Server
ClickHouse documents a fully managed remote Model Context Protocol server for ClickHouse Cloud at clickhouse.com/docs/cloud/features/ai-ml/remote-mcp. Connect MCP clients to the HTTP endpoint `https://mcp.clickhouse.cloud/mcp` with OAuth 2.0 (browser sign-in with ClickHouse Cloud credentials; no separate API key required per docs). Agents can list databases and tables, inspect schemas, and run scoped read-only SELECT queries; the remote server also exposes richer ClickHouse Cloud integration such as service management, backup monitoring, ClickPipe visibility, and billing data per ClickHouse docs. Enable per service in the Cloud console (Connect → MCP). For self-hosted ClickHouse, ClickHouse maintains the separate open-source mcp-clickhouse project—distinct from this Cloud remote MCP.
Milvus MCP Server
The zilliztech/mcp-server-milvus project (documented at milvus.io/docs/milvus_and_mcp.md) exposes Milvus vector-database operations to MCP clients such as Claude Desktop and Cursor. The recommended launch path is `uv run src/mcp_server_milvus/server.py --milvus-uri http://localhost:19530` without a separate install step, with optional `MILVUS_URI`, `MILVUS_TOKEN`, and `MILVUS_DB` environment variables. Tools listed in Milvus docs include `milvus-text-search`, `milvus-hybrid-search`, `milvus-multi-vector-search`, `milvus-query`, and `milvus-count` for collection management, semantic retrieval, filtered hybrid search, and entity counts.
Neo4j MCP Server
Neo4j documents an official Model Context Protocol server at neo4j.com/docs/mcp/current and in the neo4j/mcp repository. It gives MCP clients structured access to a Neo4j graph: get-schema introspects labels, relationship types, and property keys; read-cypher runs read-only Cypher checked with EXPLAIN and Neo4j query-type classification; write-cypher runs writes unless NEO4J_MCP_READ_ONLY=true; list-gds-procedures lists Graph Data Science procedures when GDS is installed. Prerequisites are a running Aura, Neo4j Desktop, or self-managed database plus the APOC plugin. Local clients use stdio via uvx neo4j-mcp-server or the Homebrew/binary neo4j-mcp, with NEO4J_MCP_URI, NEO4J_MCP_USERNAME, NEO4J_MCP_PASSWORD, and NEO4J_MCP_DATABASE. Aura uses HTTP at https://<instance-id>.mcp-instances.neo4j.io after Tool authentication is enabled in the Aura console. Docs also describe an HTTP transport mode that takes URI and credentials per request and selects the database from the /db/{databaseName}/mcp path.