Mindbody MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Mindbody MCP Server check if Sarah Johnson has any upcoming classes booked this week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
π§ Mindbody MCP Server
A comprehensive Model Context Protocol (MCP) server that provides AI assistants with complete access to the Mindbody API for fitness and wellness studio management. Perfect for yoga studios, pilates studios, gyms, and wellness centers.
β¨ Features
50+ Tools covering every aspect of studio operations
Complete Class Management - View schedules, book clients, manage waitlists, substitute teachers
Client Management - Add/update clients, track visits, memberships, and balances
Sales & Commerce - Process payments, sell packages, memberships, and retail products
Staff Management - View schedules, manage appointments, track availability
Multi-Location Support - Manage multiple studio locations seamlessly
High Performance - Built on Bun runtime with intelligent caching
Type-Safe - Full TypeScript support with comprehensive types
Dual Transport Support - STDIO for local development, SSE for production deployment
Related MCP server: GoHighLevel MCP Server
π Quick Start
Installation with npx (Node.js)
# Run directly without installation
npx @vespo92/mindbody-mcp
# Or install globally
npm install -g @vespo92/mindbody-mcpInstallation with bunx (Bun - 4x faster)
# Run directly without installation
bunx @vespo92/mindbody-mcp
# Or install globally with Bun
bun install -g @vespo92/mindbody-mcpInstall from GitHub
# Using npx
npx github:vespo92/MindbodyMCP
# Using bunx (recommended for performance)
bunx github:vespo92/MindbodyMCP
# Or clone and run locally
git clone https://github.com/vespo92/MindbodyMCP.git
cd MindbodyMCP
bun install # or npm install
bun run start # or npm startπ Prerequisites
Node.js 18+ or Bun 1.0+
Mindbody API credentials (API Key, Site ID, Source credentials)
Claude Desktop or any MCP-compatible client
βοΈ Configuration
1. Get Mindbody API Credentials
Sign up for a Mindbody Developer Account
Create a new app to get your API credentials
Note your Site ID (use -99 for sandbox testing)
2. Set Environment Variables
Create a .env file in your project root:
# Copy the example file
cp .env.example .env
# Edit with your credentials
MINDBODY_API_KEY=your_api_key_here
MINDBODY_SITE_ID=-99 # Your site ID
MINDBODY_SOURCE_NAME=your_source_name
MINDBODY_SOURCE_PASSWORD=your_source_password
# Optional settings
MINDBODY_API_URL=https://api.mindbodyonline.com/public/v6
CACHE_TTL_MINUTES=5
MCP_SERVER_NAME=mindbody-mcp
MCP_SERVER_VERSION=2.0.03. Configure Claude Desktop
Add to your Claude Desktop configuration:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"mindbody": {
"command": "bunx",
"args": ["@vespo92/mindbody-mcp"],
"env": {
"MINDBODY_API_KEY": "your_api_key",
"MINDBODY_SITE_ID": "-99",
"MINDBODY_SOURCE_NAME": "your_source_name",
"MINDBODY_SOURCE_PASSWORD": "your_source_password"
}
}
}
}Or use the GitHub repository directly:
{
"mcpServers": {
"mindbody": {
"command": "bunx",
"args": ["github:vespo92/MindbodyMCP"],
"env": {
"MINDBODY_API_KEY": "your_api_key",
"MINDBODY_SITE_ID": "-99",
"MINDBODY_SOURCE_NAME": "your_source_name",
"MINDBODY_SOURCE_PASSWORD": "your_source_password"
}
}
}
}π οΈ Available Tools
The server provides 50+ tools across 7 categories:
π Class Management
getClasses- View all classes with filtersgetClassDescriptions- List class typesgetClassSchedules- View recurring schedulesaddClientToClass- Book clients into classesremoveClientFromClass- Cancel bookingsgetWaitlistEntries- Manage waitlistssubstituteClassTeacher- Handle substitutions
π₯ Client Management
getClients- Search and retrieve clientsaddClient- Register new clientsupdateClient- Update client informationgetClientVisits- View attendance historygetClientMemberships- Check active membershipsaddClientArrival- Check-in clientsgetClientAccountBalances- View account balancesgetClientContracts- View contracts
π° Sales & Commerce
getServices- View available servicesgetPackages- List class packagesgetProducts- Browse retail productsgetContracts- View membership optionscheckoutShoppingCart- Process purchasespurchaseContract- Sell memberships
π’ Site & Locations
getSites- Get business informationgetLocations- List all locationsgetPrograms- View programs offeredgetResources- Manage resourcesgetSessionTypes- List session typesgetStaff- View all staff membersgetTeacherSchedule- Teacher schedules
π Appointments
getStaffAppointments- View appointmentsaddAppointment- Book appointmentsupdateAppointment- Modify appointmentsgetBookableItems- Find available slotsgetActiveSessionTimes- Check availabilitygetScheduleItems- View schedules
π Enrollments
getEnrollments- View courses/workshopsaddClientToEnrollment- Register for coursesgetClientEnrollments- View client enrollments
π¬ Example Usage in Claude
Once configured, you can ask Claude:
"Show me today's yoga classes"
"Book Sarah Johnson into the 6pm Vinyasa class"
"Who's on the waitlist for tomorrow's Hot Yoga?"
"Add a new client named Jennifer Wilson"
"What's Michael's attendance this month?"
"Process a 10-class package purchase for Amy"
"Find a substitute for Maria's Thursday class"ποΈ Development
Local Development
# Clone the repository
git clone https://github.com/vespo92/MindbodyMCP.git
cd MindbodyMCP
# Install dependencies
bun install # or npm install
# Run in development mode
bun run dev # or npm run dev
# Run tests
bun test # or npm test
# Build for production
bun run build # or npm run buildProject Structure
MindbodyMCP/
βββ src/
β βββ index.ts # Main server entry point
β βββ api/ # API client and auth
β βββ tools/ # Tool implementations
β βββ types/ # TypeScript types
β βββ cache/ # Caching layer
β βββ utils/ # Utility functions
βββ tests/ # Test files
βββ .github/workflows/ # CI/CD pipelines
βββ CLAUDE.md # Detailed documentationπ SSE Deployment (Production)
The server supports SSE (Server-Sent Events) transport for production deployment, enabling web-based clients and remote access.
Quick Start with SSE
# Start with SSE transport
bun run start:sse
# Or with environment variable
MCP_TRANSPORT=sse bun start
# With custom port
bun run src/index.ts --transport sse --port 8080Docker Deployment
# Using Docker Compose
docker-compose up -d
# Or manually
docker build -t mindbody-mcp .
docker run -d -p 3000:3000 -e MCP_TRANSPORT=sse mindbody-mcpProduction Configuration
Configure via environment variables:
MCP_TRANSPORT=sse- Enable SSE transportMCP_PORT=3000- Server portMCP_HOST=0.0.0.0- Server hostMCP_CORS_ORIGIN=https://yourdomain.com- CORS configurationMCP_SSL_CERT=/path/to/cert.pem- SSL certificate (optional)MCP_SSL_KEY=/path/to/key.pem- SSL private key (optional)
Endpoints
/health- Health check endpoint/info- Server information/sse- SSE event stream for MCP communication
For detailed deployment instructions, see SSE Deployment Guide.
π§ͺ Testing
# Run all tests
bun test
# Test SSE connection
bun run test:sse
# Test specific tool
bun run test:tool
# Run benchmarks
bun run benchmark
# Type checking
bun run typecheckπ¦ Publishing
The package is available on:
GitHub Packages: vespo92/MindbodyMCP
π Security
API credentials are stored securely via environment variables
OAuth 2.0 authentication with automatic token refresh
No credentials are logged or exposed
Regular security audits via GitHub Actions
β‘ Performance
Bun Runtime: 4x faster startup than Node.js
Intelligent Caching: 5-minute cache for dynamic data, 60-minute for static
Automatic Retry: Exponential backoff for failed requests
Rate Limiting: Respects Mindbody's 2000 requests/hour limit
π€ Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Fork the repository
Create your feature branch (
git checkout -b feature/AmazingFeature)Commit your changes (
git commit -m 'Add some AmazingFeature')Push to the branch (
git push origin feature/AmazingFeature)Open a Pull Request
π License
This project is licensed under the MIT License - see the LICENSE file for details.
π Acknowledgments
Mindbody API for providing comprehensive fitness studio APIs
Anthropic MCP SDK for the Model Context Protocol
Bun for the blazing fast JavaScript runtime
π Support
Issues: GitHub Issues
Discussions: GitHub Discussions
Email: vinnie@vespo92.com
π Roadmap
Webhook support for real-time updates
Advanced reporting and analytics tools
Multi-site synchronization
AI-powered recommendations
Mobile app integration
GraphQL API layer
Available Tools
39 toolsaddAppointmentC
Book an appointment
Inputs: staffId (required), clientId (required), locationId (required), sessionTypeId (required), +7 more.
addClientB
Add a new client
Inputs: lastName (required), firstName (required), city, email, +11 more.
addClientArrivalB
Check in a client (mark arrival)
Inputs: clientId (required), locationId (required).
addClientToClassC
Book a client into a class
Inputs: classId (required), clientId (required), waitlist, requirePayment.
addClientToEnrollmentC
Register client for course/workshop
Inputs: clientId (required), classScheduleIds (required), enroll, testMode, +4 more.
checkoutShoppingCartC
Process a shopping cart checkout
Inputs: items (required), clientId (required), payments (required), inStore, +3 more.
getActivationCodeC
Get site activation code
Inputs: no named parameters.
getActiveSessionTimesC
Get active session availability times
Inputs: days, endTime, startTime, scheduleType, +1 more.
getBookableItemsC
Get available appointment slots
Inputs: sessionTypeIds (required), endDate, staffIds, startDate, +2 more.
getClassDescriptionsB
Get all class types/descriptions offered
Inputs: no named parameters.
getClassesC
Get all classes with filtering options
Inputs: endDate, staffIds, startDate, locationIds, +1 more.
getClassSchedulesC
Get class schedules (recurring class templates)
Inputs: staffIds, programIds, locationIds, classDescriptionIds.
getClassVisitsA
Get client visits/attendance for a specific class. Returns all clients who booked or attended the class, including sign-in status, late cancellations, and service information.
Inputs: classId (required), lastModifiedDate.
getClientAccountBalancesB
Get client's account balances
Inputs: clientId (required).
getClientContractsB
Get client's contracts/memberships
Inputs: clientId (required).
getClientEnrollmentsC
Get client's enrollments
Inputs: clientId (required).
getClientMembershipsC
Get client's active memberships
Inputs: clientId (required), locationId.
getClientsC
Search and retrieve clients
Inputs: clientIds, isProspect, searchText, lastModifiedDate.
getClientVisitsC
Get client's visit/attendance history
Inputs: clientId (required), endDate, startDate.
getContractsC
Get available contracts/memberships
Inputs: locationId, soldOnline, contractIds.
getEnrollmentsC
Get enrollments (courses, workshops, series)
Inputs: endDate, staffIds, courseIds, startDate, +5 more.
getLocationsB
Get all studio locations
Inputs: no named parameters.
getPackagesC
Get class packages
Inputs: locationId, classScheduleId.
getProductsC
Get retail products
Inputs: productIds, searchText, sellOnline, categoryIds, +1 more.
getProgramsC
Get programs (yoga, pilates, etc.)
Inputs: onlineOnly, scheduleType.
getResourcesC
Get resources (rooms, equipment)
Inputs: locationId, endDateTime, startDateTime, sessionTypeIds.
getScheduleItemsC
Get schedule items/availability
Inputs: endDate, staffIds, startDate, locationIds, +1 more.
getServicesC
Get available services (class packages, memberships)
Inputs: classId, locationId, programIds, sessionTypeIds, +1 more.
getSessionTypesB
Get session types (class types, appointment types)
Inputs: onlineOnly, programIds.
getSitesB
Get site/business information
Inputs: no named parameters.
getStaffB
Get all staff members with optional filters
Inputs: filters, staffIds, locationIds, startDateTime, +1 more.
getStaffAppointmentsC
Get staff appointments
Inputs: staffIds (required), endDate, clientIds, startDate, +2 more.
getTeacherScheduleB
Get a teacher's class schedule for a specified date range
Inputs: teacherName (required), endDate, startDate.
getWaitlistEntriesC
Get waitlist entries for classes
Inputs: classIds, clientIds, classScheduleIds.
purchaseContractC
Purchase a contract/membership
Inputs: clientId (required), startDate (required), contractId (required), locationId, +3 more.
removeClientFromClassB
Cancel a client's class booking
Inputs: classId (required), clientId (required), lateCancel.
substituteClassTeacherB
Substitute a teacher for a class
Inputs: classId (required), originalTeacherId (required), substituteTeacherId (required), substituteTeacherName.
updateAppointmentC
Update an appointment
Inputs: appointmentId (required), notes, staffId, sendEmail, +5 more.
updateClientC
Update client information
Inputs: updates (required), clientId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 39 tools
Many tools have clearly distinct resources, but the scheduling and purchasing domains contain overlapping tools (e.g., getServices, getPackages, getContracts; getBookableItems, getActiveSessionTimes, getScheduleItems). Additionally, getClassVisits and getClientVisits are similar in scope, creating potential confusion.
Tool names consistently follow a verb_noun pattern (get, add, update, remove, substitute, checkout, purchase) and use camelCase throughout. Minor deviations exist in verb choice for similar actions (e.g., addClientToClass vs. addClient), but the overall structure is predictable and readable.
With 39 tools, the server exceeds the 25+ threshold considered excessive, creating a large and potentially overwhelming surface for agents. Even though Mindbody is a broad domain, the number of tools could be consolidated or split into different servers.
The tool set covers many core workflows: client management, class scheduling, appointments, enrollments, and sales. However, obvious lifecycle gaps exist, such as no delete operations for clients or appointments, no class creation/update, and no cancellation for appointments, which can lead to dead ends.
Maintenance
Related MCP Connectors
Manage fitness coaching clients, workouts, programs, chats and funnels from your assistant.
Ask your AI assistant about your class studio's own numbers. See upcoming classes and how full they are, find the classes that need promoting, and check fill rates, attendance, bookings, cancellations and revenue from classes, gift cards and private events. Read-only, and limited to the studio that connects.
Stop manually creating generic reports that don't match your gym! Ask your AI about your studio's sales, classes and clients. Mindbody MCP server for Claude and ChatGPT. Connect your studio once, then ask about sales, classes, clients and memberships. Not affiliated with Mindbody.
Read Mindbody classes, schedules, clients, staff and sales; book clients and appointments.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables AI agents to manage spa/wellness operations via Zenoti API, including appointments, guests, services, and billing.2374 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to directly interact with the entire GoHighLevel CRM via 563+ tools across 44 categories, allowing natural language control for contacts, messaging, opportunities, calendars, and more.16 npm1ISC
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query and manage Altea Active memberships through natural language, including schedules, spot availability, instructor sessions, bookings, cancellations, and waitlists.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to find gyms and studios, check schedules and prices, start trial classes, and, after OAuth sign-in, view, book, or cancel classes with a membership. Public tools require no account, while member tools enforce each gym's booking rules and never pass payment data to the assistant.MIT