Comprehensive MCP server for Mindbody API - Complete yoga studio management via AI assistants
Connect MindbodyMCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Comprehensive MCP server for Mindbody API - Complete yoga studio management via AI assistants. The mindbodymcp mcp server is what makes that connection.
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.
The server ships on npm as @vespo92/mindbody-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Endpoints — For detailed deployment instructions, see SSE Deployment GuideConfiguration is passed through the environment: MINDBODY_API_KEY, MINDBODY_SITE_ID, MINDBODY_SOURCE_NAME, MINDBODY_SOURCE_PASSWORD, MINDBODY_API_URL, MCP_SSL_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MindbodyMCP's toolset — Endpoints — is a fair guide to whether it matches your workflow. It is maintained by vespo92; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Endpoints | For detailed deployment instructions, see [SSE Deployment Guide](docs/SSE_DEPLOYMENT.md). |
{
"mcpServers": {
"mindbodymcp": {
"command": "npx",
"args": ["-y", "@vespo92/mindbody-mcp"],
"env": {
"MINDBODY_API_KEY": "your-value",
"MINDBODY_SITE_ID": "your-value",
"MINDBODY_SOURCE_NAME": "your-value",
"MINDBODY_SOURCE_PASSWORD": "your-value",
"MINDBODY_API_URL": "your-value",
"MCP_SSL_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MINDBODY_API_KEY | Credential the server authenticates with. | Yes |
| MINDBODY_SITE_ID | Configuration value read at startup. | Optional |
| MINDBODY_SOURCE_NAME | Configuration value read at startup. | Optional |
| MINDBODY_SOURCE_PASSWORD | Configuration value read at startup. | Optional |
| MINDBODY_API_URL | Endpoint or connection string the server talks to. | Yes |
| MCP_SSL_KEY | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.