ClickHouse Cloud MCP connector
The ClickHouse Cloud connector lets Claude, ChatGPT, Cursor, Microsoft Copilot 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.
- Connects over OAuth
- Free 14-day trial
- No credit card
How many rows landed in the events table yesterday?
Working in ClickHouse Cloud with Elaichi
-
Run select query
-
List databases
-
List tables
How to connect ClickHouse Cloud to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
ClickHouse Cloud MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
ClickHouse Cloud MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
ClickHouse Cloud MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
ClickHouse Cloud MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect ClickHouse Cloud to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with ClickHouse Cloud through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in ClickHouse Cloud is logged.
-
Data
Answer a numbers question without writing SQL
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.
-
Analytics
Find the table before building the report
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.
-
Platform
Check every service before the morning standup
Pull the list of services, their current state and details, and spot anything idle, stopped or unexpectedly large before anyone else notices.
-
Platform
Confirm last night's backups actually ran
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.
-
Finance
Explain the ClickHouse Cloud bill by service
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.
-
Engineering
See whether a ClickPipe is still flowing
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.
Try asking
- “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?”
What connecting ClickHouse Cloud gets you
6 screens from Elaichi, each doing one job for your ClickHouse Cloud account.
Ask Elaichi to work across your apps.
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?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask ClickHouse Cloud questions in plain language.
Row counts, service state and monthly cost answered from live tables and services.
Copy the endpoint
AI apps
One governed endpoint for every client.
Claude, ChatGPT, Cursor and Microsoft Copilot reach ClickHouse Cloud through one org endpoint, no SDK, no shared key.
Tool catalog
13 tools cover queries, services, backups and cost.
Select queries, databases, tables, backups, ClickPipes and organization cost, with no custom code.
Toolboxes
Each team gets its own ClickHouse Cloud toolbox.
Finance sees cost, Platform sees services and backups, Data runs queries.
Shared connections
Teammates query without ever seeing a credential.
One person connects ClickHouse Cloud, shares it, and everyone still signs in as themselves.
Audit log
Every query and lookup is logged by name.
When, who, what happened and which service or table, kept in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
ClickHouse Cloud digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch databases
ClickHouse Cloud
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
ClickHouse Cloud
Queued
Workflows
A schedule starts the cost review for you.
Services and cost are fetched, grouped, drafted into a digest, approved by a person, then delivered.
ClickHouse Cloud health
Refreshed 4 minutes ago · every 15 minutes · from the databases collection
Databases
1,284 ↓ 12%
Tables
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Databases created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Analytics 21%
Finance 18%
Collections and dashboards
ClickHouse Cloud health reported without being asked.
Four metrics, 14 days of backups and queries, and a team breakdown, refreshed on a schedule.
Why connect ClickHouse Cloud's MCP server through Elaichi
ClickHouse Cloud builds and runs this MCP server. Elaichi sits in front of it, so ClickHouse Cloud's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to ClickHouse Cloud's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach ClickHouse Cloud's tools at the same Elaichi address as every other connected app. Nobody adds ClickHouse Cloud's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own ClickHouse Cloud sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches ClickHouse Cloud's server. By default, a tool ClickHouse Cloud does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to ClickHouse Cloud
ClickHouse Cloud builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the ClickHouse Cloud team.
For IT and engineering
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.
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 | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
ClickHouse Cloud tools for your AI agents
13 tools are ready to call through Elaichi's MCP endpoint the moment you connect ClickHouse Cloud, governed by the same roles, restrictions, and audit log as everything else in Elaichi. ClickHouse Cloud builds and runs these tools.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 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 role that only needs cost reporting. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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.
Put ClickHouse Cloud in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot