[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Mindbody MCP server: Let your AI agent keep your Mindbody classes full. > Mindbody has an official Public API v6 and a Webhooks API, but live access needs a developer approval, an activation by each studio owner and a metered fee, and it has no official MCP server (checked 6 Nov 2026). Cotlet runs 13 Mindbody tools hosted: no API key, no developer account, and they work inside the ChatGPT and Claude apps. Connect Mindbody classes, rosters, clients and contracts to Claude or ChatGPT. Ask in plain words to rebook a cancelled class, list clients who stopped coming or report fill rates. Cotlet hosts it, with no API key and no developer setup. - Free 7-day trial, no card - Hosted 24/7, one account for many apps - Independent, not affiliated with Mindbody - Page: https://cotlet.dev/integrations/mindbody-api-mcp-server ## What can your AI agent do in Mindbody? - Rebook a cancelled class - Read rosters and waitlists - Find clients who stopped coming - Check stalled contracts - Add new leads as clients - Report weekly fill rates ## Does Mindbody have an MCP server or an API? - Mindbody's developer FAQ says the API has a limit of 1,000 calls a day, then one third of a cent per call, charged only with live clients. That page is dated 2023, so the current rate sits in the developer portal. - Going live takes a developer account, a live-access request that Mindbody approves, and then the studio owner activating the link for the site (Mindbody Webhooks guide). - Zapier lists Mindbody as "Not Yet Supported" and n8n has no Mindbody node. The Webhooks API does push class, client and sale events to a URL you host. | What you need | Public API v6 | GitHub MCP server | Cotlet | |---|---|---|---| | How you get in | Developer account, approval, owner activation | Needs the same API credentials | Your own staff login | | Classes, rosters, clients, contracts | Yes, once live | Yes, through the API | Yes | | Book, cancel, add a client | Yes, once live | Some servers, behind flags | Yes, after your OK | | Use it in the ChatGPT or Claude app | You build it | Runs on your own computer | Hosted, runs 24/7 | | Cost | Metered per call | Free, plus API calls | Credits per call, no API meter | Checked 6 Nov 2026. Sources: [Mindbody Developer FAQs](https://developers.mindbodyonline.com/resources/faqs), [Mindbody Public API V6.0](https://developers.mindbodyonline.com/PublicDocumentation/V6), [Mindbody Webhooks API Documentation](https://developers.mindbodyonline.com/WebhooksDocumentation), [Zapier: Mindbody not yet supported](https://zapier.com/apps/mindbody/integrations) ## How does the Mindbody MCP server work? 1. **Sign in to Mindbody.** Use your staff login in its Cloud Browser. 2. **Connect your AI agent.** Paste one address, approve the sign-in. 3. **Ask in plain words.** Your agent calls the Mindbody tools. We never keep your Mindbody password, and no booking, cancel or contract change goes through until you approve it. ## How to connect Mindbody to your AI agent Add one address to your agent. Chat apps sign in with Cotlet, editors and scripts use an API key. 1. **Enable Mindbody for agents.** Sign up, sign in to Mindbody in its Cloud Browser with your staff login, then press Enable for agents. 2. **Add the Cotlet address.** Paste https://cotlet.dev/mcp/v1 into your agent as an MCP server or connector. 3. **Approve the connection.** Chat apps open a Cotlet sign-in. Editors, n8n and scripts take an API key from the console. One shared address, `https://cotlet.dev/mcp/v1`, carries Mindbody along with your other apps. If you enable Mindbody after connecting, refresh the connector and the new tools appear. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-mindbody \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-mindbody": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-mindbody] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: mindbody_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: mindbody_write ``` ## All 13 Mindbody MCP tools ### Classes and rosters Dates are read in the studio's time zone. The roster lists the waitlist apart from the booked clients. - **List classes** (`list_classes`, read): Scheduled classes in a date range with time, teacher, booked count and capacity. - **Get class roster** (`get_class_roster`, read): Clients booked into one class, and its waitlist. ### Clients, visits and contracts Run search_clients before add_client to avoid a duplicate. How far back visits go follows the studio's Client History Windows setting. - **Search clients** (`search_clients`, read): Find clients by name, email or phone. - **Get client** (`get_client`, read): One client's Client Info: contact details, birthday, membership status and last and next visit. - **List client visits** (`list_client_visits`, read): A client's past visits, newest first. - **List client contracts** (`list_client_contracts`, read): A client's contracts with status, end date and autopay state. - **Add client** (`add_client`, write, asks first): Create a new client. - **Update client** (`update_client`, write): Change a client's contact details. ### Bookings and contract changes The studio's own rules still apply: a client without a valid pricing option is not booked, and a late cancel follows the studio policy. - **Book client into class** (`book_client_into_class`, write, asks first): Enroll a client in a class. - **Cancel client booking** (`cancel_client_booking`, write, asks first): Cancel one client's booking in a class. - **Terminate client contract** (`terminate_client_contract`, write, asks first): Terminate a client's contract and stop its autopays. ### Reports and staff schedule Each report needs the matching staff permission; without it the call names the missing one. - **Get attendance report** (`get_attendance_report`, read): Attendance with revenue for a date range, per class. - **List staff schedule** (`list_staff_schedule`, read): The classes each teacher is scheduled for. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/mindbody-api-mcp-server#tools ## Who can see my Mindbody session, and how do I revoke it? - **What we store.** The signed-in staff profile, AES-256-GCM encrypted, kept in Finland. Never your password. - **What your agent gets.** The 13 Mindbody tools, not the session cookie. - **What the session sees.** What your staff permissions show: schedule, clients, visits, contracts, reports. - **What no tool touches.** Card payments, selling a pricing option or contract, refunds, staff pay. - **If you are signed out.** Your agent gets a link and you sign in again yourself. - **How to cut access.** Disable for agents, reset the browser, or deactivate the staff login in Mindbody. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). ## Which Mindbody login does my agent use? The agent works in Mindbody the way a staff member does, in the same web app, under the login you sign in with. What it can do follows that login's staff permissions: Add Client to add a client, the permission to terminate client contracts to end a contract, the report permissions for the attendance report. A call without the permission fails and names it. Studios that want the agent apart from the owner create a separate staff login for it and give it only the permissions the jobs need. Mindbody then lists its changes under that name. How your Mindbody stays in your hands: - Your own staff login, signed in by you - One Cloud Browser with a steady IP and its own cookies - Adding a client, booking, cancelling and terminating a contract wait for your OK (4 tools) - No tool takes a payment or sells a contract - You switch the agent off for Mindbody in one click > The studio's own emails still go out: a booking or cancellation sends the class confirmation or cancellation email to the client if that notification is on. Read the call before you approve it. ## What happens when Mindbody changes? - **12 h** between tests of the Mindbody reads - **24 h** between tests of writes a client would notice - **$0** for a call to a Mindbody tool paused for repair When Mindbody moves a screen or renames a field, the fix happens on our side and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the roster.** The cancelled class and the later class, with places left. 2. **Checks who fits.** A client without a valid pricing option is listed, not booked. 3. **Waits for your OK.** Each booking and cancel sits in your Cotlet console first. 4. **Reports the result.** Who moved, who did not fit, who is on the waitlist. | Action | Undo | |---|---| | Book a client into a class | Cancel the booking; the studio policy decides whether an early or late cancel costs a visit | | Cancel a booking | Book the client again if there is room; the cancel stays in the history | | Update a client | Call update_client again with the old details | | Add a client | Fix the details in Client Info; no tool deletes a client | | Terminate a contract | Cancel the termination while the contract end date has not passed; after that the contract is sold again | 4 of 13 tools ask first: add_client, book_client_into_class, cancel_client_booking and terminate_client_contract. update_client reaches no one and one more call undoes it, so it runs at once. You can turn the wait off per tool, for example for a nightly lead import. > Choose cancel_type early or late with care: Mindbody applies the studio's own policy, so a late cancel can use up a visit or charge a fee. MCP call: ``` { "name": "book_client_into_class", "arguments": { "client_id": "100234", "class_id": "c_48125" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/mindbody/class/c_48125/clients/100234/into-class \ -H "Authorization: Bearer $COTLET_API_KEY" ``` Tool output: ``` { "booking_id": "b_90420", "class_id": "c_48125", "client_id": "100234", "place": "roster", "booked": 15, "capacity": 20 } ``` A cron job or script calls the same tools over REST, with the same key and the same price per call. A booking with no valid pricing option fails with the reason, and a failed call is free. Each tool in the table above shows its REST path. ## How much does the Mindbody MCP server cost? **About $23 a month** for one studio's front desk chores, 3,960 credits. Mindbody keeps billing your plan as before. | Job | Calls | Credits | |---|---|---| | Front desk roster and schedule lookups | 2 × 30 | 600 | | Rebook a cancelled class of 12 | 26 × 2 | 520 | | Find lapsed members, weekly | 13 × 4 | 520 | | Attendance and fill-rate report, weekly | 3 × 4 | 120 | | Add a new lead as a client | 2 × 20 | 400 | | Check stalled contracts | 2 × 15 | 300 | | Cloud Browser, 30 days | | 1,500 | | Total | | 3,960 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - No Mindbody API fees: Cotlet does not use the metered API Mindbody publishes no per-studio counts, so the month is our example: a studio of about 200 members and 40 classes a week, two cancelled classes, 20 new leads. Mindbody lists plans from $79 a month per location, the higher plans by quote (mindbodyonline.com, 6 Nov 2026). Dollars at the $29 pack rate. ## Mindbody MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [vespo92/MindbodyMCP](https://github.com/vespo92/MindbodyMCP) | A TypeScript MCP server with 50+ tools for classes, clients, sales and staff, 11 stars. | Runs on your computer with Public API credentials; last commit 31 Mar 2026. | | [alex454-byte/mindbody-mcp-server](https://github.com/alex454-byte/mindbody-mcp-server) | Read-only by default, masks personal data, writes behind flags, 0 stars. | Public API credentials and a local install; last commit 15 Oct 2026. | | [NoBanks/mindbody-mcp](https://github.com/NoBanks/mindbody-mcp) | Python server with 5 tools; booking and checkout are switched off by default. | Public API credentials; small tool set. | | [Pipedream](https://mcp.pipedream.com/app/mindbody) | A hosted Mindbody MCP address for chat apps. | Connects through Pipedream and the Mindbody API route. | | [Zapier](https://zapier.com/apps/mindbody/integrations) | Lists Mindbody as not yet supported; paid connectors turn Mindbody webhooks into Zaps. | Reacts to events, no agent that reads rosters or books. | The official Public API is the route for a developer who wants a custom integration and is willing to wait for approval and owner activation. Cotlet suits a studio that wants its own agent working this week, in the ChatGPT or Claude app, on the staff login it already has. ## Who runs Cotlet Take Group sp. z o.o. runs Cotlet, a software company registered in Poland, EU (VAT PL6342984273), working since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Mindbody tools go to contact@cotlet.dev. ## Mindbody MCP server: questions ### How do I connect Mindbody to ChatGPT or Claude? Sign up at cotlet.dev, log in to Mindbody once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Mindbody account through Cotlet, in their phone apps too. ### What can ChatGPT do in Mindbody? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Mindbody: rebook clients from a cancelled class; find clients who stopped coming; check clients with a stalled contract. You ask in plain words, and anything that reaches other people waits for your OK first. ### How do I get access? Create a free account at https://cotlet.dev, open Mindbody under Integrations in the console and sign in to Mindbody in its Cloud Browser. The trial starts with your first app, no card asked. ### How do I connect Mindbody to ChatGPT or Claude? Sign up at cotlet.dev, log in to Mindbody once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Mindbody account through Cotlet, in their phone apps too. ### Is there an official ChatGPT or Claude app for Mindbody? No. Mindbody has no ChatGPT or Claude connector of its own (checked 8 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account. ### Can ChatGPT book a client into a class in Mindbody? Yes, with Cotlet. ChatGPT finds the client and the class and books them in, or cancels a booking. Each booking waits for your OK by default, which you can switch off per tool. ### Can ChatGPT show the class roster in Mindbody? Yes, with Cotlet. ChatGPT lists the day's classes, reads each roster and pulls the attendance report, in your own Mindbody login. Reading sends nothing to anyone. ### What does Mindbody charge for API calls? Mindbody's developer FAQ says the API has a limit of 1,000 calls a day, then one third of a cent for every call, and that you are charged only with live clients. The FAQ is dated 2023, so check the developer portal for the current rate. Cotlet works in your own Mindbody login and does not use those API calls. ### Which login does my agent need? Your own Mindbody business login, as owner or staff. What the agent can do follows that login's staff permissions: for example, Add Client to add a client and the permission to terminate client contracts to end a contract. A call without the permission fails and names it. ### Does the agent take payments? No. The tools read classes, clients, visits and contracts, book and cancel class bookings, add and edit clients and terminate a contract. Selling a pricing option or contract and charging a card stay in Mindbody. ### Does Mindbody have webhooks? Yes, through its Webhooks API for approved developers. Cotlet has no trigger for new bookings, so run your agent on a schedule, for example a list_classes and get_class_roster pass every morning. ### Does it work for a studio with several locations? It works in the Mindbody site you sign in to, with the schedule and permissions that staff login has. ### Is the MCP server different from the REST API? Only in how you call it. Both have the same 13 tools, inputs, answers, API key and price. Agents speak MCP; scripts and HTTP steps call REST. ### Is Cotlet affiliated with Mindbody? No. Cotlet is independent and not affiliated with Mindbody. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.