How to connect Breeze to OpenClaw
Connect Breeze to OpenClaw with ClawLink: paste your Breeze key once and 18 tools work from chat. No MCP server to run, nothing stored on your machine.
BreezeAPI KEYMCPBreeze is a project management software that helps teams plan, track, and collaborate on projects efficiently.. Once connected, OpenClaw can read and act on Breeze from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Breeze 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 Breeze setup: install one ClawHub skill, connect Breeze in the browser, and OpenClaw can call real Breeze 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 Breeze.
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 Breeze
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Breeze?"
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 Breeze in the ClawLink dashboard — paste your Breeze API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Breeze, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Breeze is connected in the dashboard, that agent calls the same 18 Breeze tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Breeze MCP for OpenClaw
Looking for a Breeze MCP server for OpenClaw? ClawLink connects Breeze to OpenClaw and exposes 18 Breeze tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Breeze integration works the same way.
What the OpenClaw Breeze integration can do
18 Breeze tools are ready for OpenClaw once the account is connected. The 14 below are the ones people reach for most; your agent can call all 18.
14 of 18 Breeze tools for OpenClaw
| Tool | What it does |
|---|---|
Get card breeze_get_card | Retrieve detailed info for a specific card (task) in a project |
Get cards breeze_get_cards | Get all cards (tasks) for a specific project |
Get project breeze_get_project | Get a specific project by ID |
Get project people breeze_get_project_people | Get all users in a project |
Get projects breeze_get_projects | Retrieves a list of all active (non-archived) projects in Breeze |
Get workspace breeze_get_workspace | Get a specific workspace by ID |
Get workspaces breeze_get_workspaces | Get all workspaces |
Add project people breeze_add_project_people | Add people to a Breeze project by inviting them via email |
Archive project breeze_archive_project | Archive a specific project |
Create card breeze_create_card | Create a new card in a project |
Create list breeze_create_list | Create a new list (stage) in a Breeze project |
Create project breeze_create_project | Creates a new project in Breeze project management system |
Create workspace breeze_create_workspace | Create a new workspace |
Move card breeze_move_card | Move a card to a different stage or position |
Try it: find the Breeze tool you need
Browse the 14 Breeze tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Breeze, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Breeze, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Breeze, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Breeze, summarize it in plain English, and point out anything that needs attention.
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 Breeze working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Breeze API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Breeze 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 Breeze. | 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 Breeze actions to the runtime in a format your agent can reliably use. | 18 tools for Breeze are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Breeze 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 Breeze in the browser, and the 18 tools above work from chat. There is no SDK and no config file, and the Breeze 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 Breeze skill but can't call the tools
The ClawHub skill teaches OpenClaw about Breeze, but the calls run through the ClawLink plugin and your connected account. Make sure Breeze 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 Breeze 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 Breeze tools
Breeze 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 Breeze 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.
Breeze 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 Breeze has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Breeze integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Breeze: link your Breeze account once in the browser and OpenClaw can call the Breeze API through 18 ready-made tools — no custom code or token handling.
How do I add Breeze to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Breeze skill from ClawHub, then you click Connect in the dashboard to authorize Breeze. OpenClaw calls the tools from the next message — no config files, and the Breeze key you paste is stored server-side instead of in your environment.
How long does it take to connect Breeze to OpenClaw?
About two minutes. Sign in, click Connect next to Breeze in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Breeze 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 Breeze working from chat.
OpenClaw installed the Breeze skill but can't call the tools
The ClawHub skill teaches OpenClaw about Breeze, but the calls run through the ClawLink plugin and your connected account. Make sure Breeze 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.
