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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/reiple/clickhouse-mcp1'
If you have feedback or need assistance with the MCP directory API, please join our Discord server