A comprehensive Model Context Protocol (MCP) server that provides **two distinct capabilities**: 1. **Database Operations** - Connect to and query
A comprehensive Model Context Protocol (MCP) server that provides two distinct capabilities: 1. Database Operations - Connect to and query any ClickHouse database (local, cloud, or self-hosted) 2. Cloud Management - Complete. The chmcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
Admin — Full access to all resourcesDeveloper — Service and resource managementRead — only mode** (CLICKHOUSE_READONLY=true): Only SELECT, SHOW, DESCRIBE, EXPLAIN queriesBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 8 environment variables: CLICKHOUSE_HOST, CLICKHOUSE_PORT, CLICKHOUSE_USER, CLICKHOUSE_PASSWORD, CLICKHOUSE_SECURE, CLICKHOUSE_READONLY, CLICKHOUSE_CLOUD_KEY_ID, CLICKHOUSE_CLOUD_KEY_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Chmcp's toolset — Admin, Developer, Read — is a fair guide to whether it matches your workflow. It is maintained by oualib; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Admin | Full access to all resources |
| Developer | Service and resource management |
| Read | only mode** (CLICKHOUSE_READONLY=true): Only SELECT, SHOW, DESCRIBE, EXPLAIN queries |
{
"mcpServers": {
"chmcp": {
"command": "/path/to/uv",
"args": ["run", "--with", "chmcp", "--python", "3.13", "chmcp"],
"env": {
"CLICKHOUSE_HOST": "your-server.com",
"CLICKHOUSE_PORT": "8443",
"CLICKHOUSE_USER": "your-username",
"CLICKHOUSE_PASSWORD": "your-password",
"CLICKHOUSE_SECURE": "true",
"CLICKHOUSE_READONLY": "true"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CLICKHOUSE_HOST | Endpoint or connection string the server talks to. | Optional |
| CLICKHOUSE_PORT | Configuration value read at startup. | Optional |
| CLICKHOUSE_USER | Configuration value read at startup. | Optional |
| CLICKHOUSE_PASSWORD | Configuration value read at startup. | Optional |
| CLICKHOUSE_SECURE | Configuration value read at startup. | Optional |
| CLICKHOUSE_READONLY | Configuration value read at startup. | Optional |
| CLICKHOUSE_CLOUD_KEY_ID | Credential the server authenticates with. | Yes |
| CLICKHOUSE_CLOUD_KEY_SECRET | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.