How to connect ClickHouse to OpenClaw
Connect ClickHouse to OpenClaw with ClawLink: paste your ClickHouse key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine.
ClickHouseBASIC AUTHMCPQuery analytics databases and inspect schemas. Once connected, OpenClaw can read and act on ClickHouse from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to ClickHouse access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical ClickHouse setup: install one ClawHub skill, connect ClickHouse in the browser, and OpenClaw can call real ClickHouse actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the ClickHouse skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "ClickHouse" (hith3sh/clickhouse-analytics) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/clickhouse-analytics
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to ClickHouse.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect ClickHouse
Enter your account details in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with ClickHouse?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect ClickHouse in the ClawLink dashboard — enter your ClickHouse account details once.
Verify the connection by asking OpenClaw:
Use ClickHouse to execute query and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once ClickHouse is connected in the dashboard, that agent calls the same 6 ClickHouse tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
ClickHouse MCP for OpenClaw
Looking for a ClickHouse MCP server for OpenClaw? ClawLink connects ClickHouse to OpenClaw and exposes 6 ClickHouse tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes ClickHouse integration works the same way.
What the OpenClaw ClickHouse integration can do
6 ClickHouse tools are ready for OpenClaw once the account is connected.
All 6 ClickHouse tools for OpenClaw
| Tool | What it does |
|---|---|
Execute query clickhouse_execute_query | Run a read-only SQL query in ClickHouse |
Get database schema clickhouse_get_database_schema | Get a full schema overview for a ClickHouse database |
Get play interface clickhouse_get_play_interface | Open the ClickHouse Play interface for interactive querying |
Get table schema clickhouse_get_table_schema | Get detailed schema information for a ClickHouse table |
List databases clickhouse_list_databases | List available ClickHouse databases |
List tables clickhouse_list_tables | List tables in ClickHouse databases |
Try it: find the ClickHouse tool you need
Browse the 6 ClickHouse tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use ClickHouse to execute query and walk me through the result in plain English.
Pull the relevant data from ClickHouse, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from ClickHouse, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from ClickHouse, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual credential setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want ClickHouse working from chat.
| Manual | ClawLink | |
|---|---|---|
| Setup flow | Collect and store the right ClickHouse credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link ClickHouse without custom integration screens. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for ClickHouse. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right ClickHouse actions to the runtime in a format your agent can reliably use. | 6 tools for ClickHouse are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes ClickHouse to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect ClickHouse in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the ClickHouse key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the ClickHouse skill but can't call the tools
The ClawHub skill teaches OpenClaw about ClickHouse, but the calls run through the ClawLink plugin and your connected account. Make sure ClickHouse is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect ClickHouse from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling ClickHouse tools
ClickHouse tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every ClickHouse call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
ClickHouse returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
The setup form accepts credentials but calls still fail
Re-enter the credentials carefully and verify the account-level permissions for ClickHouse. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles.
FAQ
Is there a OpenClaw ClickHouse integration?
Yes. ClawLink is the fastest way to connect OpenClaw to ClickHouse: link your ClickHouse account once in the browser and OpenClaw can call the ClickHouse API through 6 ready-made tools — no custom code or token handling.
How do I add ClickHouse to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink ClickHouse skill from ClawHub, then you click Connect in the dashboard to authorize ClickHouse. OpenClaw calls the tools from the next message — no config files, and the ClickHouse key you paste is stored server-side instead of in your environment.
How long does it take to connect ClickHouse to OpenClaw?
About two minutes. Sign in, click Connect next to ClickHouse in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring ClickHouse up myself?
The alternative to ClawLink is usually manual credential setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want ClickHouse working from chat.
OpenClaw installed the ClickHouse skill but can't call the tools
The ClawHub skill teaches OpenClaw about ClickHouse, but the calls run through the ClawLink plugin and your connected account. Make sure ClickHouse is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
