Claude ClickHouse connectorWhat Claude can do in your ClickHouse account.
The Claude ClickHouse connector exposes 13 tools: 13 read, 0 write, 0 undescribed. They browse your ClickHouse Cloud organizations, services and table schemas, run read-only SELECT queries, and report on backups, ClickPipes and billing. ClickHouse states that none of them can modify anything.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can query ClickHouse Cloud
Answering a data question usually means finding the right service, the right database and the right table before writing any SQL. With this connector you ask in plain English, and Claude walks the structure of your ClickHouse Cloud account, writes the SELECT query, runs it against the service and explains the result, with no install on your side.
Answer a business question from raw tables. A product manager asks how many sign-ups came from each country last week; list_tables shows the columns available, and run_select_query runs the read-only query and returns the figures for Claude to comment on.
Check that backups are in shape. A data engineer wants reassurance before a migration; list_service_backups shows the latest backups and get_service_backup_configuration gives the schedule and retention settings.
Keep an eye on spend. A finance lead asks what the platform cost this month; get_organization_cost returns a grand total plus daily records per entity, which Claude turns into a short, readable summary.
What it will not do: no tool can insert or delete rows, alter a service or start a backup, and nothing runs by itself when a pipeline fails. Claude only queries while it answers you. The Integrations hub lists the platforms we document.
Five words before you connect
The vocabulary Claude uses around this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work on it while it answers you.
- Tool
- One named thing a connector lets Claude do on that account. Claude picks the ones it needs; the directory sheet lists them by name.
- Authorization
- The ClickHouse Cloud sign-in page, where you grant Claude the access it uses afterwards. Given once per person, and revocable.
- Approval
- The confirmation Claude waits for before it changes something in an account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like ClickHouse.
Connect ClickHouse to Claude in three steps
- 01
Find ClickHouse in your settings
Open Claude's settings, go to Customize, then Connectors, and look for ClickHouse. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before members can sign in individually.
- 02
Start the connection
Click Connect on its row, then sign in with your ClickHouse Cloud credentials in the browser window that opens. If the link breaks later, Disconnect and connect again to repair it.
- 03
Read the authorization screen
Check what the ClickHouse authorization screen covers before you accept. It belongs to ClickHouse, not to Claude, and the access stays limited to the organizations and services your own account can reach.
The 13 tools, grouped by what they do
ClickHouse gives Claude 13 tools: 13 that read your account, 0 that change something in it.
One group only: ClickHouse documents all thirteen as read-only, each marked as such in its own metadata. Names stay exactly as Claude shows them.
- 13 read
What Claude reads (13)
13 toolsThirteen tools that browse your account, run SELECT queries and report on services without modifying anything.
get_organizations
Lists every ClickHouse Cloud organization the signed-in user can access. It answers the first question of any session: which organization holds the service you have in mind.
get_organization_details
Returns the details of a single organization once Claude knows its identifier, so it can confirm it is looking at the right one before going further.
get_services_list
Lists all the services in one ClickHouse Cloud organization, which tells Claude where your databases actually live before it looks any deeper.
get_service_details
Zooms in on one specific service inside an organization, giving Claude the context it needs before it inspects databases, backups or ClickPipes on that service.
get_organization_cost
Retrieves billing and usage cost data for an organization: a grand total plus daily cost records for each entity, over an optional date range.
run_select_query
Executes a read-only SELECT query against a ClickHouse service and returns the rows. This is where Claude turns your plain-English question into an actual answer from your data.
list_databases
Shows all databases available in a given ClickHouse service, so Claude knows where to look for the tables your question needs.
list_tables
Lists the tables of a database together with their column definitions, which shows what a query can actually use.
list_service_backups
Lists the backups of a service, most recent first, so Claude can tell you when the last one ran and how far back they go.
get_service_backup_details
Opens a single backup picked from the backup list, for a closer look at that one snapshot rather than the whole history.
get_service_backup_configuration
Gives the backup configuration of a service, meaning its schedule and retention settings, so you can check the policy itself rather than individual snapshots one by one.
list_clickpipes
Lists all ClickPipes configured for a service, giving Claude an inventory of what is plugged into it before anyone digs into a single pipe.
get_clickpipe
Focuses on one specific ClickPipe on a service, for when a single pipe needs a closer inspection than the list provides.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. ClickHouse documents all thirteen tools here as read-only, so there is nothing for Claude to modify.
On Team and Enterprise workspaces, owners decide whether members may let some actions through without being asked each time. They can also limit what a connector may do for the whole organization, for example keeping reading and closing writing, and nobody overrides that from their own account. Claude works with the rights of the person who signed in: ClickHouse scopes the access to the organizations and services that user can reach.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. Connector by connector, that answer is published nowhere: it is a real gap in the catalogue.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before each member connects. For the current state of this one, check its sheet in the official directory, the only place showing it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing fires when a ClickPipe fails or a cost spikes.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The verification badge is not a security audit, and Anthropic states on every sheet that it does not control which tools a publisher exposes. Only ClickHouse documents this connector; no Claude help article covers it. To compare with a connector that does write, see the Claude adobe-workfront connector.
Need help connecting ClickHouse to Claude?
A person reads every message.