# How to connect Metabase to OpenClaw (paste one key, 189 tools) > Connect Metabase to OpenClaw with ClawLink: paste your Metabase key once and 189 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/metabase The usual route to Metabase 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 Metabase setup: install one ClawHub skill, connect Metabase in the browser, and OpenClaw can call real Metabase 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/metabase ## Setup It takes three steps to connect OpenClaw to Metabase. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Metabase** — 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 metabase # connect Metabase (browser OAuth) npx -y @useclawlink/cli actions metabase # list available actions npx -y @useclawlink/cli run metabase --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 Metabase in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Metabase API key once. Verify the connection by asking OpenClaw: > Create it in Metabase for me, then confirm the important fields before you finish. ### 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 Metabase is connected in the dashboard, that agent calls the same 189 Metabase 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). ## Metabase MCP for OpenClaw Looking for a Metabase MCP server for OpenClaw? ClawLink connects Metabase to OpenClaw and exposes 189 Metabase 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 Metabase integration](https://claw-link.dev/hermes/metabase) works the same way. ## What the OpenClaw Metabase integration can do 189 Metabase tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 189. ### 30 of 189 Metabase tools for OpenClaw | Tool | What it does | |---|---| | **Create bookmark** `metabase_create_bookmark` | Create a new bookmark for a Metabase item (card, dashboard, collection, or dataset) | | **Create card pivot query** `metabase_create_card_pivot_query` | Run a pivot table query on a Metabase card (question) | | **Create card query1** `metabase_create_card_query1` | Run the query associated with a Card and return its results | | **Create dashboard copy** `metabase_create_dashboard_copy` | Create a copy of an existing Metabase dashboard | | **Create dashboard pivot dashcard card** `metabase_create_dashboard_pivot_dashcard_card` | Run a pivot table query for a specific DashCard | | **Create dashboard save collection** `metabase_create_dashboard_save_collection` | Save a denormalized dashboard description into a collection | | **Create database discard values** `metabase_create_database_discard_values` | Discard all saved field values for a specific database | | **Create dataset parameter search** `metabase_create_dataset_parameter_search` | Search for parameter values in datasets when editing cards or dashboards | | **Get action** `metabase_get_action` | Retrieve a Metabase action by ID | | **Get API action** `metabase_get_api_action` | Retrieve all actions available in the Metabase instance | | **Get API activity popular items** `metabase_get_api_activity_popular_items` | Get the list of 5 popular items on the Metabase instance | | **Get API activity recent views** `metabase_get_api_activity_recent_views` | Retrieve recently viewed items in Metabase | | **Get API alert** `metabase_get_api_alert` | Retrieve all alerts in Metabase | | **Get API auto dashboards database ID candidates** `metabase_get_api_auto_dashboards_database_id_candidates` | Retrieve automagic dashboard candidates for a specific database | | **Get API bookmark** `metabase_get_api_bookmark` | Retrieve all bookmarks for the authenticated user | | **Get API card** `metabase_get_api_card` | List all cards (questions) available to the authenticated user in Metabase | | **Get API card card ID params param key search query** `metabase_get_api_card_card_id_params_param_key_search_query` | Search for values of a specific parameter in a Metabase card | | **Get API card ID** `metabase_get_api_card_id` | Retrieve a specific card (question) by its ID | | **Get API collection** `metabase_get_api_collection` | Retrieve all collections that the current user has read permissions for | | **Get API collection ID** `metabase_get_api_collection_id` | Retrieve detailed information about a Metabase collection by its ID | | **Get API collection ID items** `metabase_get_api_collection_id_items` | Retrieve items from a specific Metabase collection | | **Get API collection root** `metabase_get_api_collection_root` | Fetch the Root Collection and its top-level objects | | **Get API collection tree** `metabase_get_api_collection_tree` | Retrieve the collection tree structure from Metabase | | **Get API database ID autocomplete suggestions** `metabase_get_api_database_id_autocomplete_suggestions` | Retrieve autocomplete suggestions for table and field names in a database | | **Get API database ID metadata** `metabase_get_api_database_id_metadata` | Retrieve complete metadata for a specific database including all tables and fields | | **Get API database virtual db datasets** `metabase_get_api_database_virtual_db_datasets` | Retrieve all datasets from a Metabase virtual database | | **Get API ee audit app user audit info** `metabase_get_api_ee_audit_app_user_audit_info` | Get audit info for the current authenticated user | | **Get API ee billing** `metabase_get_api_ee_billing` | Retrieve the billing API version information for the Metabase Enterprise Edition instance | | **Get API ee dependencies graph dependents** `metabase_get_api_ee_dependencies_graph_dependents` | Get dependents of a resource in Metabase's dependency graph | | **Get API ee embedding hub checklist** `metabase_get_api_ee_embedding_hub_checklist` | Retrieve the embedding hub checklist status for Metabase Enterprise Edition | ## Example prompts **Create Bookmark** > Create it in Metabase for me, then confirm the important fields before you finish. **Create Card Pivot Query** > Create it in Metabase for me, then confirm the important fields before you finish. **Create Card Query1** > Create it in Metabase for me, then confirm the important fields before you finish. **Create Dashboard Copy** > Create it in Metabase for me, then confirm the important fields before you finish. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key 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 Metabase working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Metabase API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Metabase account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Metabase. | 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 Metabase actions to the runtime in a format your agent can reliably use. | 189 tools for Metabase are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Metabase 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 Metabase in the browser, and the 189 tools above work from chat. There is no SDK and no config file, and the Metabase 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 Metabase skill but can't call the tools The ClawHub skill teaches OpenClaw about Metabase, but the calls run through the ClawLink plugin and your connected account. Make sure Metabase 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 Metabase 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 Metabase tools Metabase 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 Metabase 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. ### Metabase 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. ### API key setup works but results look incomplete Double-check that the API key for Metabase has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Metabase integration? Yes. ClawLink is the fastest way to connect OpenClaw to Metabase: link your Metabase account once in the browser and OpenClaw can call the Metabase API through 189 ready-made tools — no custom code or token handling. ### How do I add Metabase to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Metabase skill from ClawHub, then you click Connect in the dashboard to authorize Metabase. OpenClaw calls the tools from the next message — no config files, and the Metabase key you paste is stored server-side instead of in your environment. ### How long does it take to connect Metabase to OpenClaw? About two minutes. Sign in, click Connect next to Metabase in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Metabase up myself? The alternative to ClawLink is usually manual API key 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 Metabase working from chat. ### OpenClaw installed the Metabase skill but can't call the tools The ClawHub skill teaches OpenClaw about Metabase, but the calls run through the ClawLink plugin and your connected account. Make sure Metabase 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 - [OpenClaw PostHog integration](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [DataforSEO](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Connect Twelve Data](https://claw-link.dev/openclaw/twelve-data) — Twelve Data provides a comprehensive financial data API offering real-time and historical market data for stocks, forex, cryptocurrencies, ETFs, and indices.