This server also ships inside ClickHouse Claude Code Plugin — a plugin that installs it already configured.
It cannot change anything; what matters is what it can see.
Read-only here is not a default you leave alone but the only setting there is — every tool carries the read-only annotation, and ClickHouse states that no tool can modify data, alter service configuration or perform a destructive operation. What a connected agent can see is wider than a database: three tools read tables and schemas, the other ten read the ClickHouse Cloud account around them, down to an organization's daily cost records. The identity you connect with is the dial, since the connection reaches exactly what that account or that API key already reaches — a dedicated, least-privilege key is how you narrow it.
What it is
An MCP endpoint that ClickHouse hosts and runs inside ClickHouse Cloud: a client points at the URL and signs in, and nothing is installed or run on your own machine. ClickHouse publishes two MCP servers, and this is the managed one — it works only against ClickHouse Cloud services. The other is an open-source package you install and run yourself; it reaches any ClickHouse instance, self-hosted included, and offers the query and schema tools only. If your ClickHouse is self-hosted, that one is the one that applies.
What you get
- SELECT queries against a ClickHouse Cloud service, with its databases, tables and column definitions listed first
- The ClickHouse Cloud organizations the signed-in account can reach, and the details of each one
- The services in an organization, and the details of a given service
- A service's backups, most recent first, the details of any one of them, and the backup schedule and retention settings in force
- The ClickPipes configured on a service, and the details of a given ClickPipe
- An organization's billing and usage cost data: a grand total plus daily cost records per entity, for a date range of up to 31 days
Requirements
A running ClickHouse Cloud service, with the remote MCP server switched on for that service. That is a per-service toggle in the Cloud console, done by someone whose console role lets them manage it, and the endpoint accepts no connections before it is on. Connecting then takes one of two things: a browser sign-in with ClickHouse Cloud credentials over OAuth 2.0, which reaches the organizations and services that account already has permission to reach, or a ClickHouse Cloud API key sent as HTTP Basic, for a host with no browser.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen