Mindbody MCP Server

39 tools. 9 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

9 can modify or destroy data
30 read-only
39 tools total

Community server · catalogue entry verified 29/06/2026

How to control Mindbody MCP Server ↓

What Mindbody MCP Server exposes to your agents

Read (30) Write / Execute (8) Destructive / Financial (1)
Critical Risk

The most dangerous Mindbody MCP Server tools

9 of Mindbody MCP Server's 39 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Mindbody MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Mindbody MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "removeClientFromClass": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "addAppointment": {
    "limits": [
      {
        "counter": "addappointment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "getActivationCode": {
    "limits": [
      {
        "counter": "getactivationcode_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Mindbody MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON MINDBODY →

Instant setup, no code required.

All 39 Mindbody MCP Server tools

READ 30 tools
Read getActivationCode Get site activation code Read getActiveSessionTimes Get active session availability times Read getBookableItems Get available appointment slots Read getClassDescriptions Get all class types/descriptions offered Read getClasses Get all classes with filtering options Read getClassSchedules Get class schedules (recurring class templates) Read getClassVisits Get client visits/attendance for a specific class. Returns all clients who booked or attended the class, inclu Read getClientAccountBalances Get client\ Read getClientContracts Get client\ Read getClientEnrollments Get client\ Read getClientMemberships Get client\ Read getClients Search and retrieve clients Read getClientVisits Get client\ Read getContracts Get available contracts/memberships Read getEnrollments Get enrollments (courses, workshops, series) Read getLocations Get all studio locations Read getPackages Get class packages Read getProducts Get retail products Read getPrograms Get programs (yoga, pilates, etc.) Read getResources Get resources (rooms, equipment) Read getScheduleItems Get schedule items/availability Read getServices Get available services (class packages, memberships) Read getSessionTypes Get session types (class types, appointment types) Read getSites Get site/business information Read getStaff Get all staff members with optional filters Read getStaffAppointments Get staff appointments Read getTeacherSchedule Get a teacher\ Read getWaitlistEntries Get waitlist entries for classes Read purchaseContract Purchase a contract/membership Read substituteClassTeacher Substitute a teacher for a class

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Mindbody MCP Server

Can an AI agent delete data through the Mindbody MCP Server MCP server? +

Yes. The Mindbody MCP Server server exposes 1 destructive tools including removeClientFromClass. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Mindbody MCP Server? +

The Mindbody MCP Server server has 8 write tools including addAppointment, addClient, addClientArrival. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Mindbody MCP Server.

How many tools does the Mindbody MCP Server MCP server expose? +

39 tools across 3 categories: Destructive, Read, Write. 30 are read-only. 9 can modify, create, or delete data.

How do I enforce a policy on Mindbody MCP Server? +

Register the Mindbody MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Mindbody MCP Server tool call.

Deterministic rules across all 39 Mindbody MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

39 Mindbody MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.