mcp-clickhouse-long-running
Provides tools for interacting with ClickHouse databases, including executing SQL queries, listing databases, and listing tables in a database, all with read-only access to ensure safety.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-clickhouse-long-running show me the top 10 products by sales last month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ClickHouse MCP Server
An MCP server for ClickHouse.
Features
Tools
run_select_queryExecute SQL queries on your ClickHouse cluster.
Input:
sql(string): The SQL query to execute.All ClickHouse queries are run with
readonly = 1to ensure they are safe.
list_databasesList all databases on your ClickHouse cluster.
list_tablesList all tables in a database.
Input:
database(string): The name of the database.
Related MCP server: clickhouse-mcp-server
Configuration
Open the Claude Desktop configuration file located at:
On macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonOn Windows:
%APPDATA%/Claude/claude_desktop_config.json
Add the following:
{
"mcpServers": {
"mcp-clickhouse": {
"command": "uv",
"args": [
"run",
"--with",
"mcp-clickhouse",
"--python",
"3.13",
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "<clickhouse-host>",
"CLICKHOUSE_PORT": "<clickhouse-port>",
"CLICKHOUSE_USER": "<clickhouse-user>",
"CLICKHOUSE_PASSWORD": "<clickhouse-password>",
"CLICKHOUSE_SECURE": "true",
"CLICKHOUSE_VERIFY": "true",
"CLICKHOUSE_CONNECT_TIMEOUT": "1800",
"CLICKHOUSE_SEND_RECEIVE_TIMEOUT": "1800"
}
}
}
}Update the environment variables to point to your own ClickHouse service.
Or, if you'd like to try it out with the ClickHouse SQL Playground, you can use the following config:
{
"mcpServers": {
"mcp-clickhouse": {
"command": "uv",
"args": [
"run",
"--with",
"mcp-clickhouse",
"--python",
"3.13",
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "sql-clickhouse.clickhouse.com",
"CLICKHOUSE_PORT": "8443",
"CLICKHOUSE_USER": "demo",
"CLICKHOUSE_PASSWORD": "",
"CLICKHOUSE_SECURE": "true",
"CLICKHOUSE_VERIFY": "true",
"CLICKHOUSE_CONNECT_TIMEOUT": "1800",
"CLICKHOUSE_SEND_RECEIVE_TIMEOUT": "1800"
}
}
}
}Locate the command entry for
uvand replace it with the absolute path to theuvexecutable. This ensures that the correct version ofuvis used when starting the server. On a mac, you can find this path usingwhich uv.Restart Claude Desktop to apply the changes.
Development
In
test-servicesdirectory rundocker compose up -dto start the ClickHouse cluster.Add the following variables to a
.envfile in the root of the repository.
Note: The use of the default user in this context is intended solely for local development purposes.
CLICKHOUSE_HOST=localhost
CLICKHOUSE_PORT=8123
CLICKHOUSE_USER=default
CLICKHOUSE_PASSWORD=clickhouseRun
uv syncto install the dependencies. To installuvfollow the instructions here. Then dosource .venv/bin/activate.For easy testing, you can run
mcp dev mcp_clickhouse/mcp_server.pyto start the MCP server.
Environment Variables
The following environment variables are used to configure the ClickHouse connection:
Required Variables
CLICKHOUSE_HOST: The hostname of your ClickHouse serverCLICKHOUSE_USER: The username for authenticationCLICKHOUSE_PASSWORD: The password for authentication
It is important to treat your MCP database user as you would any external client connecting to your database, granting only the minimum necessary privileges required for its operation. The use of default or administrative users should be strictly avoided at all times.
Optional Variables
CLICKHOUSE_PORT: The port number of your ClickHouse serverDefault:
8443if HTTPS is enabled,8123if disabledUsually doesn't need to be set unless using a non-standard port
CLICKHOUSE_SECURE: Enable/disable HTTPS connectionDefault:
"true"Set to
"false"for non-secure connections
CLICKHOUSE_VERIFY: Enable/disable SSL certificate verificationDefault:
"true"Set to
"false"to disable certificate verification (not recommended for production)
CLICKHOUSE_CONNECT_TIMEOUT: Connection timeout in secondsDefault:
"1800"Increase this value if you experience connection timeouts
CLICKHOUSE_SEND_RECEIVE_TIMEOUT: Send/receive timeout in secondsDefault:
"1800"Increase this value for long-running queries
CLICKHOUSE_DATABASE: Default database to useDefault: None (uses server default)
Set this to automatically connect to a specific database
Example Configurations
For local development with Docker:
# Required variables
CLICKHOUSE_HOST=localhost
CLICKHOUSE_USER=default
CLICKHOUSE_PASSWORD=clickhouse
# Optional: Override defaults for local development
CLICKHOUSE_SECURE=false # Uses port 8123 automatically
CLICKHOUSE_VERIFY=falseFor ClickHouse Cloud:
# Required variables
CLICKHOUSE_HOST=your-instance.clickhouse.cloud
CLICKHOUSE_USER=default
CLICKHOUSE_PASSWORD=your-password
# Optional: These use secure defaults
# CLICKHOUSE_SECURE=true # Uses port 8443 automatically
# CLICKHOUSE_DATABASE=your_databaseFor ClickHouse SQL Playground:
CLICKHOUSE_HOST=sql-clickhouse.clickhouse.com
CLICKHOUSE_USER=demo
CLICKHOUSE_PASSWORD=
# Uses secure defaults (HTTPS on port 8443)You can set these variables in your environment, in a .env file, or in the Claude Desktop configuration:
{
"mcpServers": {
"mcp-clickhouse": {
"command": "uv",
"args": [
"run",
"--with",
"mcp-clickhouse",
"--python",
"3.13",
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "<clickhouse-host>",
"CLICKHOUSE_USER": "<clickhouse-user>",
"CLICKHOUSE_PASSWORD": "<clickhouse-password>",
"CLICKHOUSE_DATABASE": "<optional-database>"
}
}
}
}Running tests
uv sync --all-extras --dev # install dev dependencies
uv run ruff check . # run linting
docker compose up -d test_services # start ClickHouse
uv run pytest testsYouTube Overview

Available Tools
3 toolslist_databasesB
List available ClickHouse databases
Inputs: no named parameters.
list_tablesC
List available ClickHouse tables in a database, including schema, comment, row count, and column count.
Inputs: database (required), like, not_like.
run_select_queryC
Run a SELECT query in a ClickHouse database
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list_databases for database enumeration, list_tables for table metadata within a database, and run_select_query for executing queries. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun naming pattern (list_databases, list_tables, run_select_query), using snake_case throughout. This predictability aids in understanding and usage without any deviations.
With only 3 tools, the server feels thin for a database interaction scope, lacking operations like data manipulation (INSERT/UPDATE/DELETE), schema modification, or query execution beyond SELECT. While core functions are present, the count is borderline low for comprehensive database management.
The tool set is significantly incomplete for ClickHouse database operations, covering only listing and SELECT queries. Missing are essential CRUD operations (e.g., INSERT, UPDATE, DELETE), schema changes (CREATE/ALTER/DROP), and other query types (e.g., SHOW, DESCRIBE), which will likely cause agent failures in broader workflows.
Maintenance
Related MCP Connectors
MCP observability: analyse MCP server usage, investigate sessions, and instrument MCP servers.
Hosted BigQuery MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Paid remote MCP for schema drift checks, approvals, receipts, and release audit logs.
MCP server for querying and analyzing data from ad platforms, analytics tools, and spreadsheets
Related MCP Servers
- Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables interaction with ClickHouse databases via MCP, providing tools to list databases and tables and execute safe SELECT, SHOW, and DESCRIBE queries.78 npmMIT
- AlicenseAqualityDmaintenanceA DataOps-focused MCP server for ClickHouse that provides query optimization advice, pipeline latency analysis, and data quality monitoring, with read-only safety.825 PyPIMIT
- FlicenseAqualityDmaintenanceRead-only MCP server for ClickHouse that allows listing databases and tables, describing schemas, and running SELECT queries.4-