Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Mindbody to Claude Code

Let Claude book clients and manage your schedule in Mindbody. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Mindbody to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Mindbody, you add a Mindbody MCP server: a small hosted service that exposes Mindbody's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Mindbody account. No API keys pasted into config files.

claude mcp add --transport http mindbody https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Mindbody once connected?

Full read-write Mindbody access lets Claude add a client to a class, check someone in, book or cancel an appointment, update a client profile, and sell a membership or class pack, all once you approve. The lookups and admin work that used to mean clicking through the dashboard happen where your bookings already live.

  • Book a client into a class or appointment and add them to a waitlist if it is full
  • Check a client in or cancel a reservation when plans change
  • Create or update a client profile with contact and contract details
  • Sell a membership, class pack, or pricing option to an existing client
  • Update a class on the schedule, including staff, capacity, or time
  • Look up a client's visit history and remaining session balance

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Mindbody access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Mindbody API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Mindbody changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Mindbody connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Mindbody connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Mindbody account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Mindbody's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Mindbody?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Mindbody account it signs in with. Revoking access is one click in Mindbody.

More on the Mindbody connector

Mindbody connector for claude.aiCustom CRM + Claude CodeStripe + Claude CodeCalendly + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us