Integration · Research and analyze

ClickHouse Cloud and Meteor AI agents

Connect ClickHouse Cloud to a Met: list databases and tables, run read only SELECT queries and check backups and costs with the official MCP server.

Book a demo See every integration

How does ClickHouse Cloud connect to Meteor?

With the ClickHouse Cloud ready-made connector, your Met uses ClickHouse's official MCP server with your account, authorized once with OAuth, on the services where you enabled MCP. It can list your organizations and services, see a service's databases and a database's tables with their columns, and run SELECT queries to answer questions such as sales by day or orders by city. It also checks a service's status, its backups and their configuration, your ClickPipes and the organization's cost in ranges of up to 31 days. All 13 tools are read only: the Met cannot change or delete data.

What it automates

What a Meteor Met does with ClickHouse Cloud

Answer a business question with your data

The owner asks how much was sold yesterday by city. The Met finds the sales table, reads its columns and runs a SELECT query that groups by city.

Learn the database before querying

If nobody told it where the data is, the Met lists the service's databases and each one's tables with their columns, instead of guessing names.

Check whether a service is healthy

When the technical team has a doubt, the Met gets the service's status and its latest backup, and says when it was taken.

Know what the week cost

The Met checks the organization's cost for the range it is asked about, up to 31 days, and answers with the total and the days that weighed the most.

13 tools

Everything your Met can ask ClickHouse Cloud for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`run_select_query`	Runs a read only SELECT query against a ClickHouse service.
`list_databases`	Lists the databases in a ClickHouse service.
`list_tables`	Lists a database's tables with their column definitions, filtered by name if you need it.
`get_organizations`	Gets the ClickHouse Cloud organizations your user can reach.
`get_organization_details`	Gets an organization's details.
`get_services_list`	Lists the services in a ClickHouse Cloud organization.
`get_service_details`	Gets a service's details.
`list_service_backups`	Lists a service's backups, most recent first.
`get_service_backup_details`	Gets a backup's details.
`get_service_backup_configuration`	Gets a service's backup configuration, with its schedule and retention.
`list_clickpipes`	Lists the ClickPipes configured on a service.
`get_clickpipe`	Gets a ClickPipe's details.
`get_organization_cost`	Gets an organization's cost and usage, with the total and daily detail, in ranges of up to 31 days.

The limits

What the ClickHouse Cloud integration does NOT do

We would rather say it here than have you find out during rollout.

It does not change or delete data: run_select_query only accepts SELECT and all 13 tools are read only. Loading or fixing data still goes through your own processes.
It does not query a service without MCP enabled: it has to be turned on for each service in the ClickHouse Cloud console, and that needs an admin permission.
It does not create services, backups or ClickPipes: it lists them and gets their details, but managing them stays in the console.
It does not get more than 31 days of cost in a single request: ClickHouse limits that range, so a quarter is requested in parts.

Before you start

What you need to connect ClickHouse Cloud

1

A ClickHouse Cloud service with MCP enabled

In the ClickHouse Cloud console, open the service, go to Connect, choose Connect with MCP and turn the toggle on. Doing so needs the control-plane:service:manage-mcp permission.
2

Connect it in Met

In Met, open Connections → ClickHouse Cloud → Connect, sign in to ClickHouse Cloud and authorize access.