Integration

ClickHouse Cloud integration

ClickHouse Cloud management API. Read the organization behind an API key, list and inspect ClickHouse services, create them, rename them, edit their IP access list and tags, start, stop or wake them, change their autoscaling band, read their backups, manage organization API keys and members, browse the organization activity log and pull the daily usage cost report in ClickHouse Credits. This integration covers the control plane only: running SQL happens on the per-service HTTPS endpoint with a database user and password, which is a different credential from the key used here.

Connect ClickHouse Cloud How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in ClickHouse Cloud.Built from the 18 ClickHouse Cloud tools below, on the connection you add once.

Common ClickHouse Cloud use cases

auditing which keys are unused
finding out who deleted a service
expanding a suspicious audit entry
finding the latest backup to restore
opening a service to a new office IP
tearing down a temporary environment
charging back credit spend per service
stopping a development service overnight
waiting until a service finishes starting
provisioning a scoped key for a CI pipeline

What you can do with ClickHouse Cloud

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Service, 7 operations

create_serviceCreate servicePOSTCreates a ClickHouse service in a provider and region and returns its generated password.
delete_serviceDelete serviceDELETEDeletes a service that is already stopped.
get_serviceGet serviceGETReturns the full description of one ClickHouse service, including its state and endpoints.
list_servicesList servicesGETLists every ClickHouse service of an organization with its state and connection endpoints.
update_serviceUpdate servicePATCHRenames a service or edits its IP access list, tags, endpoints and release channel.
update_service_scalingUpdate service scalingPATCHChanges the memory band, replica count and idle behaviour of a service.
update_service_stateUpdate service statePATCHSends a start, stop or awake command to a service.

Activity, 2 operations

get_activityGet activityGETReturns a single audit event with its actor and target.
list_activitiesList activitiesGETLists organization audit events, optionally within a date range.

Api key, 2 operations

create_api_keyCreate api keyPOSTCreates an organization API key and returns its id and secret once.
list_api_keysList api keysGETLists the organization API keys with their state, roles and last use.

Backup, 2 operations

get_backupGet backupGETReturns the status, size and duration of one backup.
list_backupsList backupsGETLists the backups of a service, newest first.

Organization, 2 operations

get_organizationGet organizationGETReturns the name, creation date and private endpoint list of an organization.
list_organizationsList organizationsGETReturns the organization the key belongs to, with its identifier.

Member, 1 operation

list_membersList membersGETLists the people in the organization with their role and join date.

Query endpoint, 1 operation

get_query_endpoint_configGet query endpoint configGETReturns which API keys and roles may run the saved queries exposed by a service.

Usage cost, 1 operation

get_usage_costGet usage costGETReturns per day and per entity usage cost in ClickHouse Credits for a date range.

Use ClickHouse Cloud from Claude Code, Cursor or Codex

Connect ClickHouse Cloud in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its ClickHouse Cloud operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect ClickHouse Cloud

Create your workspace
Sign up free. Nothing to install.
Connect ClickHouse Cloud once
Add your ClickHouse Cloud connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

ClickHouse Cloud integration FAQ

What can you do with the ClickHouse Cloud integration?

LiveContext exposes 18 operations on ClickHouse Cloud, covering service, activity, api key and backup. Common uses include auditing which keys are unused, finding out who deleted a service and expanding a suspicious audit entry.