mindbody-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MINDBODY_API_KEY | Yes | Your Mindbody Developer API key | |
| MINDBODY_SITE_ID | Yes | Your Mindbody site ID (use -99 for sandbox) | |
| MINDBODY_USER_TOKEN | No | Your Mindbody staff user token (optional but required for client + write actions) | |
| MINDBODY_ALLOW_BOOKINGS | No | Set to 'true' to enable booking writes (class enrollment and appointment scheduling) | false |
| MINDBODY_ALLOW_CHECKOUT | No | Set to 'true' to enable payment processing (separate flag for safety) | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_client_infoB | Fetch detailed profile information for a Mindbody client. Used by AI front-desk agents to ground responses in customer history. |
| list_classesA | Query class schedules and active class lists within a date range. Used by AI scheduling agents to surface available classes to a caller. |
| book_client_to_classA | Enroll a client into an upcoming studio class. GATED behind MINDBODY_ALLOW_BOOKINGS env var. Returns an error if not enabled. This action results in a real reservation. |
| book_appointmentA | Schedule a single wellness or training appointment for a client with a specific staff member at a specific time. GATED behind MINDBODY_ALLOW_BOOKINGS. Returns an error if not enabled. |
| checkout_shopping_cartA | Process purchases and complete payment checkout for passes, services, or products. GATED behind MINDBODY_ALLOW_CHECKOUT env var. This action TAKES PAYMENT from the client. Returns an error if not enabled. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct action: booking an appointment, booking a class, processing payment, fetching client info, and listing classes. No functional overlap.
All tools use consistent snake_case verb_noun pattern (book_appointment, book_client_to_class, checkout_shopping_cart, get_client_info, list_classes).
5 tools is well within the ideal 3-15 range and covers core scheduling and client operations without feeling sparse or bloated.
Covers basic booking and client info but lacks cancel/modify appointments, staff listing, or class search beyond listing. Notable gaps for full lifecycle management.