What are the 5 ways to connect Mindbody to Claude in 2026?

What are the options?

Five. The first is built only for Mindbody, the next three are platforms that connect many apps besides Mindbody, and the last is code you run yourself.

1. 1.

   StudioVector

   Built only for Mindbody

   A hosted connection made for studio owners. Sign up with Google or your email, approve one activation link in Mindbody, and add one link in Claude or ChatGPT.

   Best for: Studio owners who want their own reports and answers across every location, without a developer account.

   Pros

   • No Mindbody developer account, API key or API bill: StudioVector holds the key and pays Mindbody's $0.002-a-call API fee, which your plan covers.
   • Report tools built for studios, such as studio_kpis, attendance_with_revenue, enrollment_fill and new_clients_summary, return a summary in one step instead of raw records.
   • Every location and every Mindbody site you connect, with unlimited locations and team seats on every plan.
   • The same link works in Claude and ChatGPT.

   Cons

   • Mindbody only: it does not connect your other apps.
   • Today the tools only read, so your AI does not book classes or change client records through it.
   • A paid plan after a free trial of 14 days from when your studio connects, or 500 credits, counted in credits: 1 credit is 1 Mindbody request that got an answer.

   See how StudioVector works

2. 2.

   Composio

   A tool platform for hundreds of apps

   A platform that connects AI agents to hundreds of apps. Its Mindbody toolkit lists 18 tools, each wrapping one Mindbody endpoint.

   Best for: Developers building an agent that uses Mindbody alongside many other apps.

   Pros

   • One connection for hundreds of apps, not just Mindbody.
   • A free plan with 100,000 tool calls a month, according to its pricing page.
   • Can make changes: its tools include adding a client to a class, removing one, and creating a client.

   Cons

   • You bring your own Mindbody API key, so Mindbody bills its API fee to you: $0.002 a call once your developer account passes 5,000 calls in a month. Composio's page says Mindbody requires you to configure your own key.
   • Its tools return Mindbody's records one endpoint at a time, so for a report the AI pages through them and does the math itself.
   • Its Find Clients tool looks clients up by known ID. Composio says it cannot search for or discover unknown clients.

   Composio's own page

3. 3.

   AnythingMCP

   A hosted connector gateway, EU-hosted

   A gateway for many connectors, made by helpcode.ai. Its Mindbody connector lists 46 tools.

   Best for: Teams that want the AI to book and update records in Mindbody, from one EU-hosted gateway.

   Pros

   • The longest Mindbody tool list here: it books classes, appointments and enrollments, creates and updates clients, and checks clients in.
   • EU-hosted, with an option to run it on your own servers.
   • A 7-day free trial.

   Cons

   • Needs your own Mindbody developer account and API key, your site ID, and a staff member's user name and password. AnythingMCP puts setup at about 10 minutes.
   • Its tools map to Mindbody endpoints, so a report across locations means many calls that the AI combines itself.
   • Mindbody bills its API fee to your own developer account: $0.002 a call once you pass 5,000 calls in a month.

   AnythingMCP's own page

4. 4.

   Vinkius

   A managed connector cloud

   A cloud of managed connectors. Its Mindbody connector lists 15 capabilities for looking up classes, sales, clients, appointments, enrollments and staff.

   Best for: Teams that run many managed connectors and want central controls over what agents do and spend.

   Pros

   • One link for every AI client, and many other managed connectors under the same account.
   • Vinkius says one switch stops every agent at once, and spending limits pause instead of billing.
   • Plans are priced by calls a month, starting at 5,000.

   Cons

   • The 15 capabilities are lookups such as list classes, list sales and search clients, so the AI builds each report from raw lists.
   • You subscribe first, then give Vinkius your Mindbody credentials.
   • Vinkius lists two Mindbody connectors with different capability lists (15 and 10), so check which one you activate.

   Vinkius's own page

5. 5.

   Open-source servers on GitHub

   Code you run yourself

   Free, MIT-licensed servers you run on your own computer. alex454-byte/mindbody-mcp-server reads only unless you turn writes on, and masks client contact details. vespo92/MindbodyMCP lists 50+ tools, including booking and checkout.

   Best for: Developers who want full control and are comfortable running and maintaining a server.

   Pros

   • Free and open source: you can read the code and change it.
   • You choose what the AI may do, from reads only to booking and checkout.
   • No third party between Mindbody and your AI client.

   Cons

   • You need your own Mindbody developer account and API key, the site owner's activation, and staff or source credentials, and you pay Mindbody's API fee: $0.002 a call once you pass 5,000 calls in a month.
   • Most run on your own computer with Claude Desktop or Claude Code. Sharing one with your team means hosting it yourself.
   • You maintain it: updates, security fixes and Mindbody API changes are up to you or the project's author.

   Open-source servers on GitHub's own page

Which one should you pick?

Pick by who will use it and what the AI needs to do. For a studio owner who wants reports, the shortest path is StudioVector.

You run a studio and want your reports across every location

StudioVector. No developer account, report tools built for studios, and every location and site in one answer, in Claude or ChatGPT.

You need the AI to book or change records in Mindbody

AnythingMCP, Composio, or an open-source server with writes turned on. Each needs your own Mindbody developer account.

You are building an agent across many apps

Composio, AnythingMCP or Vinkius, which connect many apps besides Mindbody.

You want to run and change the code yourself

An open-source server from GitHub.

What does every option need from Mindbody?

The business owner's approval. With StudioVector, the owner approves one activation link and StudioVector holds the API key. With the other four, you first create a Mindbody developer account and API key, request live access, and then the owner activates your developer source for the site.

Live data also has an API fee. Mindbody's developer FAQ lists $0.002 per request, billed monthly: a month under 5,000 requests costs nothing, and a month over 5,000 charges every request, the first 5,000 included. StudioVector pays it, and your plan covers it. With your own developer account, Mindbody bills it to you.

How do you get access to the Mindbody API?

How did we compare them?

We make StudioVector. What we say about the other four comes from their own pages and READMEs, read on November 9, 2026 and listed under Sources. Products change quickly, so check their pages before you choose, and tell us if something here is out of date.

Sources and official instructions

• Composio: Mindbody toolkit
• Composio docs: Mindbody tools
• Composio: pricing
• AnythingMCP: Mindbody connector
• AnythingMCP: connect Mindbody to Claude
• AnythingMCP: pricing
• Vinkius: Mindbody connector
• Vinkius: Mindbody Health & Wellness connector
• Vinkius: pricing
• GitHub: alex454-byte/mindbody-mcp-server
• GitHub: vespo92/MindbodyMCP
• Mindbody developer FAQ: API access fee

Common questions