ClickHouse MCP server for AI apps

What your AI apps can do with ClickHouse

Explore databases and tables
Run analytical SQL queries

ClickHouse MCP tools

13 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`run_select_query`	Run a SELECT query against a ClickHouse service (read-only)
`list_databases`	List the databases in a service (read-only)
`list_tables`	List tables in a database with column definitions, optionally filtered (read-only)
`get_organizations`	Get the Cloud organizations you can access (read-only)
`get_organization_details`	Get details of one organization (read-only)
`get_services_list`	List the services in an organization (read-only)
`get_service_details`	Get details of one service (read-only)
`list_service_backups`	List a service's backups, newest first (read-only)
`get_service_backup_details`	Get details of one backup (read-only)
`get_service_backup_configuration`	Get a service's backup schedule and retention settings (read-only)
`list_clickpipes`	List the ClickPipes configured for a service (read-only)
`get_clickpipe`	Get details of one ClickPipe (read-only)
`get_organization_cost`	Get an organization's cost and usage data for up to 31 days (read-only)

Suggested access for each AI app

The documentation this list comes from doesn't mark ClickHouse's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same ClickHouse connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add ClickHouse to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every ClickHouse tool, give Cursor only the read tools, or keep ClickHouse away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the ClickHouse MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect ClickHouse in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the ClickHouse endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http clickhouse 'https://mcp.clickhouse.cloud/mcp'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "clickhouse": {
      "url": "https://mcp.clickhouse.cloud/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the ClickHouse MCP documentation for what your client needs.

Before you connect

A ClickHouse account. Sign-in uses your ClickHouse permissions.

Server details

Detail	Value
Publisher	ClickHouse
Endpoint	`https://mcp.clickhouse.cloud/mcp`
Authentication	Browser sign-in
Categories	Data & infrastructure
Tool list	13 tools, observed 29 October 2026 (docs)

ClickHouse MCP documentation

ClickHouse MCP server for Claude, Codex and Cursor