Bring Booking System
to CrewAI
Learn how to connect Mindbody to CrewAI and start using 15 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the Mindbody MCP Server?
Connect your Mindbody business to any AI agent and run your fitness studio, spa, or wellness center through natural conversation.
What you can do
- Classes — View schedules, class types, upcoming sessions, and instructor assignments
- Appointments — Browse booked appointments, check staff availability, and manage private sessions
- Clients — Search members, view visit history, check memberships, and track attendance patterns
- Staff — List instructors and therapists with bios, certifications, and assigned services
- Sales — Track revenue, view transactions, browse retail products, and check pricing options
- Site — Access business details, multiple locations, and session types
- Enrollments — Monitor multi-week courses, workshops, and teacher training programs
Who is this for?
- Studio Owners — Get instant business insights, revenue summaries, and attendance trends
- Front Desk Staff — Search clients, check schedules, and answer member questions instantly
- Fitness Managers — Monitor class fill rates, instructor performance, and member retention
- Multi-Location Operators — Compare performance across all your locations in one conversation
Built-in capabilities (15)
Shows attendance patterns, no-shows, and engagement over time. Critical for retention analysis. Get client visit history
Shows remaining visits, expiration dates, and auto-pay status. Get client memberships and packages
Get studio/business info
) with client name, staff, time, duration, and status. Filter by date range or staff member. List booked appointments
Useful for understanding the studio's regular weekly cadence. List recurring class schedules
g. Vinyasa Yoga, CrossFit WOD, Spin). Includes name, category, description, and duration. List all class types/descriptions
Filter by date range or class type. Essential for seeing the studio schedule at a glance. List scheduled classes
Includes dates, capacity, pricing, and enrolled clients. List course enrollments
Includes address, phone, tax rates, and operating hours. List studio locations
Includes name, price, category, and inventory count. List retail products
Includes amount, payment method, client, and date. Essential for revenue tracking. List sales transactions
Shows price, session count, and expiration policy. List services and pricing options
Includes name, bio, photo URL, certifications, and assigned services. List all staff and instructors
Useful for viewing availability, managing bookings, or planning coverage. Get a staff member's appointment schedule
Returns demographics, contact info, account balance, and membership status. The core CRM tool for studio owners. Search studio clients/members
Why CrewAI?
When paired with CrewAI, Mindbody becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Mindbody tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Mindbody in CrewAI
Mindbody and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Mindbody to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Mindbody in CrewAI
The Mindbody MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 15 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Mindbody for CrewAI
Every tool call from CrewAI to the Mindbody MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I get my Mindbody API Key?
Sign up at developers.mindbodyonline.com, create a developer account, then go to Account → API Credentials to generate your API Key. You'll also need the Site ID of the business you want to connect to.
What is a Site ID and where do I find it?
The Site ID is a unique numeric identifier for each Mindbody business. The business owner can find it in their Mindbody account under Settings. For testing, use Site ID '-99' which is the Mindbody sandbox.
Can I book classes or appointments through the AI agent?
Currently the server focuses on read operations for maximum safety. Write operations (booking, canceling) are planned for v2 and will require the optional User Token credential with staff-level permissions.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.