# ClickHouse Cloud MCP connector The ClickHouse Cloud connector lets Claude, ChatGPT, Cursor and the Elaichi Agent run select queries, browse databases and tables, and check services, backups, ClickPipes and organization cost, with every call made as the person who signed in. Source: https://elaichi.ai/connectors/clickhouse-cloud/ ## Facts | | | | --- | --- | | Application | ClickHouse Cloud | | Category | Database | | AI tools | 13 | | Authentication | Connects over OAuth | | Bring your own OAuth app | No | | Native MCP | Yes. ClickHouse Cloud builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top | | Support for its tools | clickhouse.com/company/contact | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once ClickHouse Cloud is connected - How many rows landed in the events table yesterday? - Which services have no backup in the last 24 hours? - What did our organization spend on ClickHouse Cloud this month? ## Connect ClickHouse Cloud in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick ClickHouse Cloud. 2. Optionally set Share with, then press Connect. 3. Approve it in ClickHouse Cloud. ClickHouse Cloud's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which ClickHouse Cloud tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## ClickHouse Cloud MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## ClickHouse Cloud MCP connector for ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## ClickHouse Cloud MCP connector for Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect ClickHouse Cloud to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a ClickHouse Cloud tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with ClickHouse Cloud through Elaichi ### Answer a numbers question without writing SQL Data. Ask how many orders landed yesterday or which region grew fastest, and the agent runs a select query against the right table and reports the figure back in plain language. ### Find the table before building the report Analytics. Browse the databases and tables in a ClickHouse Cloud service to see what is actually there, then pull a quick sample so the report is built on the right source. ### Check every service before the morning standup Platform. Pull the list of services, their current state and details, and spot anything idle, stopped or unexpectedly large before anyone else notices. ### Confirm last night's backups actually ran Platform. List the backups for a service, open the latest one, and check the backup configuration so you can say with confidence that the data is protected. ### Explain the ClickHouse Cloud bill by service Finance. Pull the organization cost and break it down by service so the monthly review starts with real figures rather than a screenshot from the console. ### See whether a ClickPipe is still flowing Engineering. List the ClickPipes in a service, open the one feeding the events table, and confirm it is healthy before a downstream team starts asking why the dashboard is stale. ## Elaichi vs Zapier MCP vs Composio for ClickHouse Cloud All three can connect ClickHouse Cloud to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay. | What to check | Elaichi | Zapier MCP | Composio | | --- | --- | --- | --- | | Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. | | Control over ClickHouse Cloud tools | Allow or restrict single ClickHouse Cloud tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. | | Record of calls | One audit entry per ClickHouse Cloud call. | A History tab of tool calls. | A log of every tool call. | | Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. | | Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. | Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## Frequently asked questions ### How do I connect ClickHouse Cloud to Claude? In Elaichi, pick ClickHouse Cloud from the catalog and sign in to ClickHouse Cloud over OAuth in the window that opens, with no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can then query your ClickHouse Cloud databases and read your services as you. ### Does ClickHouse Cloud work with ChatGPT and Cursor as well as Claude? Yes. ClickHouse Cloud is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, any other MCP client, or used by the Elaichi Agent. There is nothing to set up per client. ### What can an AI agent actually do with my ClickHouse Cloud data? It can run select queries against your ClickHouse Cloud tables and give you the answer in plain language, list the databases and tables in a service, and check services, backups, backup configuration, ClickPipes and organization cost. Short concrete asks work best, such as the row count for one table or the cost for one month. It reads; it does not write, drop or alter anything. ### Does connecting ClickHouse Cloud give the AI everything in my organization? No. The AI works inside the ClickHouse Cloud access of the person who signed in, so it sees only the organizations, services and tables that person can already see. Elaichi can narrow that further, for example to cost and service views only, but it can never widen it beyond what ClickHouse Cloud already allows. ### Can my team share one ClickHouse Cloud connection? Yes. One person connects ClickHouse Cloud in Elaichi and shares it with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so every query and every service lookup is logged under their own name. ### Can I stop an agent from deleting or changing things in ClickHouse Cloud? The ClickHouse Cloud connector only runs select queries and reads services, backups, ClickPipes and cost, so there is no delete or change action to begin with. You can restrict any individual action further in Elaichi, such as turning off queries for a team that only needs cost reporting. A restricted action is never shown to Claude, ChatGPT or Cursor, so no prompt can reach it. ### What happens to a ClickHouse Cloud connection when someone leaves? Offboarding that person in Elaichi ends their access to ClickHouse Cloud through every client at once. A shared ClickHouse Cloud connection keeps working for everyone else on the team. Disconnecting ClickHouse Cloud once in Elaichi removes it from Claude, ChatGPT, Cursor and the Elaichi Agent together. ### Does the ClickHouse Cloud MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. ClickHouse Cloud is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs. ### Is Elaichi an alternative to Zapier MCP for ClickHouse Cloud? Yes. Both let Claude, ChatGPT or Cursor use ClickHouse Cloud. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every ClickHouse Cloud call. ### How is Elaichi different from Composio for ClickHouse Cloud? Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to ClickHouse Cloud: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call. ## All 13 ClickHouse Cloud tools Every tool below is callable through https://api.elaichi.ai/mcp once ClickHouse Cloud is connected, subject to the toolbox it is in and the restrictions on the caller. - **Run select query** (Search). Execute a read-only SELECT query against a ClickHouse service. - **List databases** (List). List all databases available in a ClickHouse service. - **List tables** (List). List all tables in a database, including column definitions. - **Get organizations** (Get). Retrieve all ClickHouse Cloud organizations accessible to the authenticated user. - **Get organization details** (Get). Return details of a single organization. - **Get services list** (Get). List all services in a ClickHouse Cloud organization. - **Get service details** (Get). Return details of a specific service. - **List service backups** (List). List all backups for a service, most recent first. - **Get service backup details** (Get). Return details of a single backup. - **Get service backup configuration** (Get). Return the backup configuration for a service (schedule and retention settings). - **List clickpipes** (List). List all ClickPipes configured for a service. - **Get clickpipe** (Get). Return details of a specific ClickPipe. - **Get organization cost** (Get). Retrieve billing and usage cost data for an organization. Returns a grand total and daily per-entity cost records.