Aleph
Query live FP&A data, build reports and update dashboards from your AI assistant.
Run read-only SELECT queries and inspect services, backups, ClickPipes and billing in ClickHouse Cloud.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The ClickHouse MCP server connects a ClickHouse Cloud account to Claude, ChatGPT and any MCP-compatible agent. Its 13 tools run read-only SELECT queries against a service and read the control plane around it — organizations, services, backups, ClickPipes and billing costs. Sign-in is OAuth against ClickHouse Cloud, and an administrator must enable the server per service first.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.
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.
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.
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.
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.
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.
.md suffix; the directory's documentation URL clickhouse.com/docs/cloud/features/ai-ml/remote-mcp redirects here) · retrieved 2026-08-18readonly, allow_ddl) — https://clickhouse.com/docs/concepts/features/configuration/settings/permissions-for-queries (fetched 2026-08-18) · retrieved 2026-08-18GET probe — 2026-08-18, HTTP 401 with www-authenticate naming resource_metadata · retrieved 2026-08-18clickhouse.com/robots.txt allows all paths except /admin/ and /marketo-forms/, names a sitemap, and carries no Content-Signal directive on any axis (fetched 2026-08-18) · retrieved 2026-08-18Connect ClickHouse once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.