# How to connect Craft to OpenClaw (no API keys) > Connect Craft to OpenClaw with ClawLink in one click — 3 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/craft The usual route to Craft 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 Craft setup: install one ClawHub skill, connect Craft in the browser, and OpenClaw can call real Craft 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 Craft. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Craft** — 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 craft # connect Craft (browser OAuth) npx -y @useclawlink/cli actions craft # list available actions npx -y @useclawlink/cli run craft --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 Craft in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use Craft to mcp craft read 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 Craft is connected in the dashboard, that agent calls the same 3 Craft 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). ## Craft MCP for OpenClaw Looking for a Craft MCP server for OpenClaw? ClawLink connects Craft to OpenClaw and exposes 3 Craft 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 Craft integration](https://claw-link.dev/hermes/craft) works the same way. ## What the OpenClaw Craft integration can do 3 Craft tools are ready for OpenClaw once the account is connected. ### All 3 Craft tools for OpenClaw | Tool | What it does | |---|---| | **Mcp craft read** `craft_mcp_craft_read` | Read/search Craft; batch with semicolons | | **Mcp blocks revert** `craft_mcp_blocks_revert` | Reverts a previous mutation if blocks haven't been modified since | | **Mcp craft write** `craft_mcp_craft_write` | Write; batch semicolons | ## Example prompts **Mcp Craft Read** > Use Craft to mcp craft read and walk me through the result in plain English. **Mcp Blocks Revert** > Use Craft to mcp blocks revert and walk me through the result in plain English. **Mcp Craft Write** > Use Craft to mcp craft write and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app 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 Craft working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Craft app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Craft through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Craft. | 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 Craft actions to the runtime in a format your agent can reliably use. | 3 tools for Craft are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Craft 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 Craft in the browser, and the 3 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Craft skill but can't call the tools The ClawHub skill teaches OpenClaw about Craft, but the calls run through the ClawLink plugin and your connected account. Make sure Craft 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 Craft 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 Craft tools Craft 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 Craft 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. ### Craft 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. ### OAuth finished in the browser but the account is still missing Try reconnecting Craft and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Craft integration? Yes. ClawLink is the fastest way to connect OpenClaw to Craft: link your Craft account once in the browser and OpenClaw can call the Craft API through 3 ready-made tools — no custom code or token handling. ### How do I add Craft to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Craft skill from ClawHub, then you click Connect in the dashboard to authorize Craft. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Craft to OpenClaw? About two minutes. Sign in, click Connect next to Craft in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Craft up myself? The alternative to ClawLink is usually manual OAuth app 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 Craft working from chat. ### OpenClaw installed the Craft skill but can't call the tools The ClawHub skill teaches OpenClaw about Craft, but the calls run through the ClawLink plugin and your connected account. Make sure Craft 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 - [Trello](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [Connect Moco](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [OpenClaw ClickUp integration](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints