ClickHouse Cloudvf.sr

listing.by · home.legend.verified

Run read-only SQL queries and inspect databases, tables and schemas on your ClickHouse Cloud services.

state.auth.long (state.auth.title)Streamable HTTP

listing.connect

listing.explain.oauth

https://mcp.clickhouse.cloud/mcp

listing.note.oauth

listing.share.h

listing.share.p

mcp.tc/i/clickhouse-cloud

listing.about

This is the managed remote MCP server for ClickHouse Cloud. It lets an assistant list databases and tables, inspect schemas and run read-only SELECT queries against your ClickHouse Cloud services. Tool calls run with the permissions of the signed-in user.

It runs as a hosted streamable HTTP endpoint at https://mcp.clickhouse.cloud/mcp. MCP must first be enabled for each service in the ClickHouse Cloud console. Users sign in with OAuth, and a ClickHouse Cloud API key can be used instead for headless clients. It is separate from the local mcp-clickhouse server.

listing.can

  • List databases and tables in a ClickHouse Cloud service
  • Inspect table schemas
  • Run read-only SELECT queries
  • Authenticate per user with OAuth
  • Use a Cloud API key for headless clients

listing.tools

listing.notools.oauth

listing.prompts

  • List the databases and tables in my ClickHouse Cloud service.

  • Show the schema of the events table.

  • Run a SELECT counting rows per day in the last week from the logs table.

  • Which tables in analytics have a timestamp column?

listing.setup.h

listing.setup.oauth

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http clickhouse-cloud https://mcp.clickhouse.cloud/mcp
  1. Start Claude Code, type /mcp, pick clickhouse-cloud and choose Authenticate. A browser window opens for the ClickHouse sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it ClickHouse Cloud and paste this URL:
https://mcp.clickhouse.cloud/mcp
  1. Click Add, then Connect, and sign in when ClickHouse asks.

Claude Desktop's JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://mcp.clickhouse.cloud/mcp and click Add.
  2. Click Connect and sign in when ClickHouse asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://mcp.clickhouse.cloud/mcp as the server URL and choose OAuth. ChatGPT sends you to ClickHouse to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

Cursor shows Needs login next to the server. Click it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"clickhouse-cloud","type":"http","url":"https://mcp.clickhouse.cloud/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "clickhouse-cloud": {
      "type": "http",
      "url": "https://mcp.clickhouse.cloud/mcp"
    }
  }
}

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "clickhouse-cloud": {
      "serverUrl": "https://mcp.clickhouse.cloud/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add clickhouse-cloud --url https://mcp.clickhouse.cloud/mcp
codex mcp login clickhouse-cloud

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.clickhouse-cloud]
url = "https://mcp.clickhouse.cloud/mcp"

Gemini CLI

gemini mcp add --transport http clickhouse-cloud https://mcp.clickhouse.cloud/mcp

Then, inside Gemini CLI, run /mcp auth clickhouse-cloud to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI's settings file.

{
  "mcpServers": {
    "clickhouse-cloud": {
      "type": "http",
      "url": "https://mcp.clickhouse.cloud/mcp"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.clickhouse.cloud/mcp.

listing.faq

Can I paste mcp.tc/i/clickhouse-cloud into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.clickhouse.cloud/mcp, so your client talks to ClickHouse Cloud directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does ClickHouse Cloud need an API key or a sign-in?

Yes, you need a ClickHouse account. The first time your client connects, it opens ClickHouse's sign-in page. The token goes straight to the server's own URL, never through mcp.tc.

Is ClickHouse Cloud a remote or a local server?

Remote. ClickHouse hosts it at https://mcp.clickhouse.cloud/mcp, and it speaks Streamable HTTP. There's nothing to install.

What can ClickHouse Cloud do?

You can list databases and tables in a ClickHouse Cloud service, inspect table schemas and run read-only SELECT queries.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc's robot read ClickHouse Cloud's own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![ClickHouse Cloud on mcp.tc](https://mcp.tc/i/clickhouse-cloud/badge.svg)](https://mcp.tc/i/clickhouse-cloud)
HTML
<a href="https://mcp.tc/i/clickhouse-cloud"><img src="https://mcp.tc/i/clickhouse-cloud/badge.svg" alt="ClickHouse Cloud on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/clickhouse-cloud.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/clickhouse-cloud" title="ClickHouse Cloud on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json

https://mcp.tc/i/clickhouse-cloud.json

listing.em.fields

listing.disclaimer_checked