Claude + Mindbody: What the Integration Can (and Can't) Do in 2026
No — there’s no official Claude Mindbody connector and no Mindbody-built MCP server. Mindbody isn’t in Anthropic’s connectors directory, and developers.mindbodyonline.com publishes a Public API v6 and a Webhooks API but no MCP. What exists on the Claude side is a tiny community MCP server (around 4 GitHub stars). Two things make Mindbody harder than the other field-service tools: the API is approval-gated and metered — live access needs a 1–2 week review plus per-site activation and per-call fees. And even connected, a Claude MCP setup only works inside a conversation you start — nothing watches your studio or acts while you’re away.
Here’s what’s actually available, the gates and costs, the limits, and what to use if you want Mindbody work that runs on its own.
The gate: approval, per-site activation, and a per-call bill
Mindbody’s API isn’t a paste-your-key affair. Getting Claude to real studio data means clearing three hurdles:
- A separate developer account — created independently from your Mindbody business account at developers.mindbodyonline.com.
- Approval for live access — the sandbox is free and self-serve (capped at 1,000 calls/day), but live data requires a “Request Live Access” application and roughly 1–2 weeks of review, where you describe your use case.
- Per-site activation and metered fees — each connection uses a site-specific activation code that the studio owner must activate, and pricing runs $11 per integration per location (entitling 1,000 calls/day/location) plus $0.002 per API call beyond that. An agent polling Mindbody has a literal per-call bill.
So a “connect Claude to Mindbody in five minutes” claim is only true against the sandbox. Live data stands behind approval, activation, and metering.
What Mindbody ships — and what it doesn’t
The Public API v6 covers classes, clients, sales, and scheduling, and there’s a separate Consumer API for marketplace/booking-facing use. The Webhooks API (documented at developers.mindbodyonline.com) fires on class, client, and sale events — good grounding for trigger workflows, once you’re past the gate.
What you won’t find is anything Claude-native. Mindbody’s AI story is its own Messenger AI, a 24/7 front desk that answers calls and texts and books classes. It’s an in-product feature — not an MCP server, and it doesn’t connect to Claude.
One naming note so you don’t get tripped up: in 2025 Mindbody, ClassPass, and Booker were rebranded under a new parent, Playlist, and on March 31, 2026 Playlist merged with EGYM. That’s corporate structure — it doesn’t change the API story.
How you’d actually connect Claude to Mindbody today
No first-party path exists, so the options are unofficial and gated:
- A community MCP server — the notable one (~4 stars, a Bun.js server against Public API v6, pitched at yoga and pilates studios, with SSE transport) still needs your Public API credentials and live-access approval to touch real data.
- Your own server — get sandbox credentials to prototype, then apply for live access and point a local MCP server at API v6.
Either adds Mindbody as a custom MCP connector. Remote custom connectors on claude.ai require a paid Claude plan; local servers run through Claude Desktop or Claude Code. No mainstream Zapier/Pipedream MCP for Mindbody surfaced in this pass, so the middleware shortcut that helps with the other tools isn’t available here.
The limits that actually matter
Even past the gate, the shape is “an assistant you operate,” not “an agent that runs.” Three limits define it:
- No triggers, no monitoring. Mindbody’s webhooks can fire on a new booking or a cancellation, but Claude’s MCP tools only run inside a conversation you start — there’s nothing to catch that webhook and act. No “when a client cancels, offer the spot to the waitlist.” You have to be in the chat, prompting.
- Conversation-only. Claude pulls a class roster or looks up a client when you ask; it doesn’t sit on your account watching bookings and following up. Close the chat and nothing continues.
- Laptop-bound for anything scheduled. The closest thing to “running on its own” is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events. That’s not an always-on, event-driven front-desk agent — and every poll it makes costs $0.002.
So Claude is good for “summarize this week’s class attendance” and not built for “fill every cancellation from the waitlist automatically.”
If you want Mindbody work that runs on its own: Carly
The moment you want something to happen around Mindbody without you in the chat — email a client the instant they book their first class, offer a cancelled spot to the waitlist, send a weekly attendance summary — you’ve crossed past what Claude’s MCP setup is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- Fires on Mindbody events or a schedule, 24/7, in the cloud — when a client books, cancels, or buys a package, Carly acts; your laptop doesn’t need to be awake.
- Runs the whole follow-up — read the booking, draft the welcome or waitlist offer, send it, and update your records off a single event.
- Actually sends and updates — drafts and sends email (Gmail and Outlook) with attachments, files and labels, manages tasks, updates your CRM, and records meetings.
- Builds the workflow for you — tell it “I’d like to email a welcome note whenever someone books their first class” in plain English; it interviews you, then builds it with you. No prompt engineering.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. Carly connects to 200+ tools across 40+ categories — see integrations. Carly natively integrates with Mindbody.
Claude vs Carly
| Claude (community MCP) | Carly | |
|---|---|---|
| Look up classes & clients | Yes (post-approval) | Yes |
| Summarize attendance | Yes | Yes |
| Acts on Mindbody triggers / events | No | Yes |
| Fills cancellations from waitlist on its own | No | Yes |
| Works while laptop is closed | No | Yes (cloud) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Official Mindbody support | No (community) | Yes (native) |
| Pricing | Pro $20 / Max $100–$200 (+ Mindbody API fees) | AI agents from $35/mo |
Claude with a community MCP is a Mindbody lookup inside a chat. Carly is a teammate that acts on bookings and cancellations as they happen.
Frequently Asked Questions
Does Claude work with Mindbody?
Not officially. There’s no Claude Mindbody connector and no Mindbody-built MCP server. You can connect them through a small community MCP server against the Public API v6 — but it’s unofficial, live data needs Mindbody’s 1–2 week approval plus per-site activation and per-call fees, and like all MCP setups it only works inside a conversation you start.
How much does the Mindbody API cost?
The sandbox is free (capped at 1,000 calls/day). Live access runs $11 per integration per location plus $0.002 per API call beyond the daily allotment — so an agent that polls Mindbody has a real per-call bill.
Isn’t Messenger AI a Claude integration?
No. Messenger AI is Mindbody’s own in-product front-desk AI. It’s not an MCP server and it doesn’t connect to your Claude account.
What if I want Mindbody to act on its own — welcome new clients, fill cancellations?
That’s outside what Claude’s MCP setup does; it responds inside a chat and doesn’t act on webhooks. Carly fires on Mindbody events and schedules 24/7 in the cloud and can email clients, offer waitlist spots, update records, and send summaries. AI agents start at $35/month.
More: Claude connectors · Claude + SimplePractice · Claude + Housecall Pro · Can Claude send emails · Claude vs Carly · Best AI personal assistants
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
