How to connect Mindbody to OpenClaw
Connect Mindbody to OpenClaw with ClawLink: paste your Mindbody key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
MindbodyAPI KEYMCPMindbody provides scheduling, client management, commerce, and business operations software for fitness, wellness, and beauty businesses.. Once connected, OpenClaw can read and act on Mindbody from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Mindbody 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 Mindbody setup: install one ClawHub skill, connect Mindbody in the browser, and OpenClaw can call real Mindbody 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 Mindbody.
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 Mindbody
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Mindbody?"
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 Mindbody in the ClawLink dashboard — paste your Mindbody API key once.
Verify the connection by asking OpenClaw:
List the relevant items in Mindbody, group them by priority, and recommend what OpenClaw should do next.
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 Mindbody is connected in the dashboard, that agent calls the same 8 Mindbody tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Mindbody MCP for OpenClaw
Looking for a Mindbody MCP server for OpenClaw? ClawLink connects Mindbody to OpenClaw and exposes 8 Mindbody tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Mindbody integration works the same way.
What the OpenClaw Mindbody integration can do
8 Mindbody tools are ready for OpenClaw once the account is connected.
All 8 Mindbody tools for OpenClaw
| Tool | What it does |
|---|---|
List accessible sites mindbody_list_accessible_sites | List Mindbody sites accessible to the connected API key, or retrieve fuller details by |
List active session times mindbody_list_active_session_times | List configured business-hour time slots and booking increments |
List classes mindbody_list_classes | Search scheduled class instances by date, location, program, session type, instructor, or known |
List enrollments mindbody_list_enrollments | Search scheduled multi-session enrollments such as workshops and events by date and business |
List locations mindbody_list_locations | List physical or online locations configured for the connected Mindbody site |
List session types mindbody_list_session_types | List service and session types configured at the connected Mindbody site, including IDs used by |
List staff mindbody_list_staff | List basic staff directory records available to the connected API key, with optional role |
Search products mindbody_search_products | Search the connected site's read-only retail product catalog by text, IDs, categories |
Try it: find the Mindbody tool you need
Browse the 8 Mindbody tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
List the relevant items in Mindbody, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Mindbody, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Mindbody, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Mindbody, 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 Mindbody working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Mindbody API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Mindbody 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 Mindbody. | 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 Mindbody actions to the runtime in a format your agent can reliably use. | 8 tools for Mindbody are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Mindbody 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 Mindbody in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Mindbody 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 Mindbody skill but can't call the tools
The ClawHub skill teaches OpenClaw about Mindbody, but the calls run through the ClawLink plugin and your connected account. Make sure Mindbody 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 Mindbody 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 Mindbody tools
Mindbody 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 Mindbody 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.
Mindbody 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 Mindbody 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 Mindbody integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Mindbody: link your Mindbody account once in the browser and OpenClaw can call the Mindbody API through 8 ready-made tools — no custom code or token handling.
How do I add Mindbody to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Mindbody skill from ClawHub, then you click Connect in the dashboard to authorize Mindbody. OpenClaw calls the tools from the next message — no config files, and the Mindbody key you paste is stored server-side instead of in your environment.
How long does it take to connect Mindbody to OpenClaw?
About two minutes. Sign in, click Connect next to Mindbody in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Mindbody 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 Mindbody working from chat.
OpenClaw installed the Mindbody skill but can't call the tools
The ClawHub skill teaches OpenClaw about Mindbody, but the calls run through the ClawLink plugin and your connected account. Make sure Mindbody 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.
