# How to connect ClickHouse to OpenClaw (paste one key, 6 tools) > 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. Web version: https://claw-link.dev/openclaw/clickhouse 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. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/clickhouse ## Setup It takes three steps to connect OpenClaw to ClickHouse. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect ClickHouse** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect clickhouse # connect ClickHouse (browser OAuth) npx -y @useclawlink/cli actions clickhouse # list available actions npx -y @useclawlink/cli run clickhouse --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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](https://claw-link.dev/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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/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](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes ClickHouse integration](https://claw-link.dev/hermes/clickhouse) 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 | ## Example prompts **Execute Query** > Use ClickHouse to execute query and walk me through the result in plain English. **Get Database Schema** > Pull the relevant data from ClickHouse, summarize it in plain English, and point out anything that needs attention. **Get Play Interface** > Pull the relevant data from ClickHouse, summarize it in plain English, and point out anything that needs attention. **Get Table Schema** > 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### 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. ### 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. ## Related - [Box](https://claw-link.dev/openclaw/box) — Store, share, and manage files and folders - [Connect Supabase](https://claw-link.dev/openclaw/supabase) — Query and manage Postgres databases - [Connect Dropbox](https://claw-link.dev/openclaw/dropbox) — Store, sync, and share files