Skip to main content
Glama
jvanvalkenhoef

clickhouse-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLICKHOUSE_URLNoThe URL of the ClickHouse serverhttp://localhost:8123
CLICKHOUSE_PASSWORDNoThe password for ClickHouse authentication
CLICKHOUSE_USERNAMENoThe username for ClickHouse authenticationdefault

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_databasesA

List all databases in ClickHouse.

list_tablesA

List tables in a database.

describe_tableA

Describe the columns and types of a table.

show_create_tableA

Return the CREATE TABLE statement for a table (schema, engine, settings).

sample_rowsA

Read a small sample of rows from a table to understand its shape. Defaults to 10 rows.

queryA

Run a read-only SQL query against ClickHouse (SELECT/WITH/SHOW/DESCRIBE/EXPLAIN only). Results are capped to keep the agent's context small. Use it to investigate telemetry: group by time, aggregate, find anomalies, join logs/metrics/traces. Add LIMIT on big tables.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct operation: listing databases, listing tables, sampling rows, describing columns, showing the CREATE statement, and running arbitrary queries. While describe_table and show_create_table both expose schema information, their purposes are clearly separated by level of detail and use case. No two tools are likely to be confused.

Naming Consistency4/5

The tool names mostly follow a consistent verb_noun pattern (list_databases, list_tables, describe_table, show_create_table, sample_rows). The exception is 'query', which is a single verb, but it is a reasonable outlier given its generic nature. Overall, the naming is predictable and easy to navigate.

Tool Count5/5

Six tools is an ideal size for a ClickHouse exploration server, covering all essential read-only operations without unnecessary bloat. Each tool has a clear purpose and none feel redundant. The count is well-scoped for the server's stated goal of investigating telemetry data.

Completeness5/5

The tool set provides full coverage for the core workflows: discovering databases and tables, understanding table schemas via describe and CREATE statements, sampling data, and running arbitrary queries for deeper analysis. There are no obvious gaps for a read-only data exploration server; any additional needs can be fulfilled through the query tool.

Maintenance

ActivitySlowing
ResponsivenessNo issues