clickhouse-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLICKHOUSE_HOST | No | ClickHouse host | localhost |
| CLICKHOUSE_PORT | No | HTTP port | 8123 |
| CLICKHOUSE_USER | No | Username | default |
| CLICKHOUSE_SECURE | No | true for HTTPS (usually port 8443) | false |
| CLICKHOUSE_DATABASE | No | Default database | default |
| CLICKHOUSE_PASSWORD | No | Password |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_databasesA | List all databases available on the ClickHouse server. |
| list_tablesA | List tables in a database (defaults to the connection's default database). Returns table name, engine, and total row count for each table. |
| describe_tableB | Describe the columns of a table: name, type, default expression, comment. |
| run_select_queryA | Run a read-only SQL query (SELECT/SHOW/DESCRIBE/EXISTS/...) against ClickHouse. Results are capped at max_rows (default 1000, hard cap 10000) and the response's "truncated" field reports whether rows were cut off. Data-modifying statements are rejected before reaching the server, and the connection is additionally opened in ClickHouse's server-side readonly mode as a second layer of enforcement. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a unique and clearly defined purpose. There is no overlap; an agent can easily distinguish between describing a table, listing databases, listing tables, and running arbitrary queries.
All tool names follow a consistent verb_noun pattern (describe, list, list, run). The naming is predictable and intuitive.
With four tools, the server is well-scoped for its read-only metadata and querying purpose. Each tool is essential and provides a distinct function without unnecessary bloat.
The tool set covers the core operations for inspecting a ClickHouse server's schema and executing queries. While some advanced metadata operations (e.g., listing table engines) are missing, the generic run_select_query tool can compensate for many gaps, making the surface reasonably complete.