# ClickHouse Cloud MCP server > Run read-only SQL queries and inspect databases, tables and schemas on your ClickHouse Cloud services. - Listing: https://mcp.tc/i/clickhouse-cloud - Connect: use the server's own URL `https://mcp.clickhouse.cloud/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Databases & Backend](https://mcp.tc/c/databases) - Vendor: ClickHouse - Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe. - Homepage: ## 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. ## What it can do - 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 ## Example 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?" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http clickhouse-cloud https://mcp.clickhouse.cloud/mcp ``` 2. 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: ```url https://mcp.clickhouse.cloud/mcp ``` 3. 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: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.clickhouse.cloud/mcp` and click **Add**. 3. 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 [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```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 [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash 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`: ```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`: ```json { "mcpServers": { "clickhouse-cloud": { "serverUrl": "https://mcp.clickhouse.cloud/mcp" } } } ``` 2. 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 ```bash codex mcp add clickhouse-cloud --url https://mcp.clickhouse.cloud/mcp codex mcp login clickhouse-cloud ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.clickhouse-cloud] url = "https://mcp.clickhouse.cloud/mcp" ``` ### Gemini CLI ```bash 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. ```json { "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`. ## Details - Last checked: 2026-10-03 (reachable, asks for credentials) - Listed: 2026-10-03 - Updated: 2026-10-04 --- Source: https://mcp.tc/i/clickhouse-cloud (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report