# How to connect Bread & Butter to OpenClaw (paste one key, 8 tools) > Connect Bread & Butter to OpenClaw with ClawLink: paste your Bread & Butter key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/bread-butter The usual route to Bread & Butter 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 Bread & Butter setup: install one ClawHub skill, connect Bread & Butter in the browser, and OpenClaw can call real Bread & Butter actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Bread & Butter. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Bread & Butter** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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 bread-butter # connect Bread & Butter (browser OAuth) npx -y @useclawlink/cli actions bread-butter # list available actions npx -y @useclawlink/cli run bread-butter --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 Bread & Butter in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Bread & Butter API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Bread & Butter, summarize it in plain English, and point out anything that needs attention. ### 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 Bread & Butter is connected in the dashboard, that agent calls the same 8 Bread & Butter 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). ## Bread & Butter MCP for OpenClaw Looking for a Bread & Butter MCP server for OpenClaw? ClawLink connects Bread & Butter to OpenClaw and exposes 8 Bread & Butter 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 Bread & Butter integration](https://claw-link.dev/hermes/bread-butter) works the same way. ## What the OpenClaw Bread & Butter integration can do 8 Bread & Butter tools are ready for OpenClaw once the account is connected. ### All 8 Bread & Butter tools for OpenClaw | Tool | What it does | |---|---| | **Get application** `bread_butter_get_application` | Return settings, feature flags, plan details, and lead-status definitions for the application | | **Get attribution report** `bread_butter_get_attribution_report` | Return visitor and conversion attribution metrics by reporting period and source for the | | **Get user insights** `bread_butter_get_user_insights` | Return aggregate attribution and user-journey insights for the connected application, with | | **List applications** `bread_butter_list_applications` | List Bread & Butter applications available to the connected credentials, optionally filtering | | **List event definitions** `bread_butter_list_event_definitions` | List configured event definitions for the connected application, optionally filtering by | | **List events** `bread_butter_list_events` | List tracked activity events for the connected application, optionally scoped to a user or date | | **List lead lists** `bread_butter_list_lead_lists` | Return the saved lead lists configured for the application bound to the connected credentials | | **List leads** `bread_butter_list_leads` | List lead and visitor profiles for the connected application, optionally filtering by email | ## Example prompts **Get Application** > Pull the relevant data from Bread & Butter, summarize it in plain English, and point out anything that needs attention. **Get Attribution Report** > Pull the relevant data from Bread & Butter, summarize it in plain English, and point out anything that needs attention. **Get User Insights** > Pull the relevant data from Bread & Butter, summarize it in plain English, and point out anything that needs attention. **List Applications** > List the relevant items in Bread & Butter, group them by priority, and recommend what OpenClaw should do next. ## 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 Bread & Butter working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Bread & Butter API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bread & Butter 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 Bread & Butter. | 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 Bread & Butter actions to the runtime in a format your agent can reliably use. | 8 tools for Bread & Butter are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Bread & Butter 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 Bread & Butter in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Bread & Butter 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 Bread & Butter skill but can't call the tools The ClawHub skill teaches OpenClaw about Bread & Butter, but the calls run through the ClawLink plugin and your connected account. Make sure Bread & Butter 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 Bread & Butter 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 Bread & Butter tools Bread & Butter 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 Bread & Butter 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. ### Bread & Butter 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 Bread & Butter has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Bread & Butter integration? Yes. ClawLink is the fastest way to connect OpenClaw to Bread & Butter: link your Bread & Butter account once in the browser and OpenClaw can call the Bread & Butter API through 8 ready-made tools — no custom code or token handling. ### How do I add Bread & Butter to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bread & Butter skill from ClawHub, then you click Connect in the dashboard to authorize Bread & Butter. OpenClaw calls the tools from the next message — no config files, and the Bread & Butter key you paste is stored server-side instead of in your environment. ### How long does it take to connect Bread & Butter to OpenClaw? About two minutes. Sign in, click Connect next to Bread & Butter in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Bread & Butter 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 Bread & Butter working from chat. ### OpenClaw installed the Bread & Butter skill but can't call the tools The ClawHub skill teaches OpenClaw about Bread & Butter, but the calls run through the ClawLink plugin and your connected account. Make sure Bread & Butter 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 - [PostHog](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [OpenClaw DataforSEO integration](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.