ClickHouse
by ClickHouse
Run read-only SELECT queries and inspect services, backups, ClickPipes and billing in ClickHouse Cloud from your AI assistant. 13 tools, all documented read-only, OAuth sign-in, off by default per service.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect ClickHouse via MCP
https://mcp.clickhouse.cloud/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
ClickHouse Tools & Capabilities (13)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Frequently asked questions
Can the ClickHouse MCP server modify or delete my data?
No, according to ClickHouse's own documentation. Its remote MCP page states every tool is read-only and annotated `readOnlyHint: true`, and says no tool can modify data, alter service configuration or perform a destructive operation. We could not confirm the annotations ourselves because the endpoint returned HTTP 401 to an anonymous handshake on 2026-08-18.
Is `run_select_query` actually limited to SELECT, or is that just the name?
ClickHouse documents it as limited to SELECT. Its setup guide states the tool only permits SELECT statements and that all queries are read-only. The vendor does not publish which mechanism enforces that on the hosted server. ClickHouse does ship an engine-level `readonly=1` session setting that permits only read queries, and its open-source MCP server documents using exactly that.
Can an AI assistant see my ClickHouse Cloud bill?
Yes, through one tool. `get_organization_cost` returns a grand total plus daily per-entity cost records for an organization, over a range capped at 31 days. ClickHouse documents billing visibility as belonging to the Admin and Billing organization roles, so a connection signed in as a plain Member is unlikely to reach it.
Do I need a paid ClickHouse Cloud plan for the MCP server?
You need a running ClickHouse Cloud service. The setup guide lists that as the only prerequisite besides an MCP client, and remote MCP appears in no row of ClickHouse's Basic, Scale and Enterprise tier comparison table, so it is not documented as gated to a paid tier. Self-hosted ClickHouse cannot use this endpoint at all.
Why does my ClickHouse MCP connection fail even though I signed in?
The server is probably not enabled on the service. ClickHouse documents remote MCP as off until an administrator turns it on per service, through Connect then MCP in the Cloud console. Access is then scoped to whatever organizations and services the signed-in user already has permission to reach, so a Member with no service role sees nothing.
What is the difference between the ClickHouse remote and open-source MCP servers?
Scope and hosting. The remote server is managed by ClickHouse Cloud, reached over streamable HTTP with OAuth, and exposes 13 tools covering queries, services, backups, ClickPipes and billing. The open-source `mcp-clickhouse` server runs locally over stdio against any ClickHouse instance, and its README documents write access as an opt-in environment variable.
Sources
- ClickHouse remote MCP in Cloud — https://clickhouse.com/docs/products/cloud/features/ai-ml/remote-mcp (fetched 2026-08-18 as Markdown via the
.mdsuffix; the directory'sdocumentationURLclickhouse.com/docs/cloud/features/ai-ml/remote-mcpredirects here) · retrieved 2026-08-18 - ClickHouse remote MCP setup guide — https://clickhouse.com/docs/products/cloud/features/ai-ml/mcp/remote-mcp (fetched 2026-08-18) · retrieved 2026-08-18
- ClickHouse permissions for queries (
readonly,allow_ddl) — https://clickhouse.com/docs/concepts/features/configuration/settings/permissions-for-queries (fetched 2026-08-18) · retrieved 2026-08-18 - ClickHouse Cloud tiers — https://clickhouse.com/docs/products/cloud/features/cloud-tiers (fetched 2026-08-18) · retrieved 2026-08-18
- ClickHouse console roles and permissions — https://clickhouse.com/docs/products/cloud/reference/security/console-roles (fetched 2026-08-18) · retrieved 2026-08-18
- ClickHouse ClickPipes overview — https://clickhouse.com/docs/integrations/clickpipes/home (fetched 2026-08-18) · retrieved 2026-08-18
- ClickHouse open-source MCP server README — https://github.com/ClickHouse/mcp-clickhouse (fetched 2026-08-18) · retrieved 2026-08-18
- Live RFC 9728 protected-resource descriptor — https://mcp.clickhouse.cloud/.well-known/oauth-protected-resource/mcp (fetched 2026-08-18) · retrieved 2026-08-18
- Live RFC 9728 host-level descriptor — https://mcp.clickhouse.cloud/.well-known/oauth-protected-resource (fetched 2026-08-18) · retrieved 2026-08-18
- Live RFC 8414 authorization-server metadata — https://mcp.clickhouse.cloud/.well-known/oauth-authorization-server (fetched 2026-08-18) · retrieved 2026-08-18
- Live anonymous
GETprobe — 2026-08-18, HTTP 401 withwww-authenticatenamingresource_metadata· retrieved 2026-08-18 - Anthropic connector directory — https://claude.ai/directory/01adc2b5-5676-4dda-9e32-2cce63929d5c (snapshot 2026-08-16) · retrieved 2026-08-16
clickhouse.com/robots.txtallows all paths except/admin/and/marketo-forms/, names a sitemap, and carries noContent-Signaldirective on any axis (fetched 2026-08-18) · retrieved 2026-08-18- ClickHouse docs machine index — https://clickhouse.com/docs/llms.txt (fetched 2026-08-18) · retrieved 2026-08-18
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Analytics
- Developer
- ClickHouse
- Tools
- 13
- Domain
- mcp.clickhouse.cloud
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.