Mindbody MCP by usefulapi

The add/get/list/update split plus resource-specific nouns makes most tools clearly distinct, and descriptions actively disambiguate tricky pairs (list_classes = occurrences vs list_class_schedules = templates vs get_class_visits = roster; list_services = pricing options vs list_session_types = bookable kinds). Minor overlap remains between mindbody_list_staff (can find available staff for a session type) and mindbody_list_bookable_items, and between the three visit-listing tools, but descriptions resolve these.

All 20 tools follow a uniform mindbody_<verb>_<noun> snake_case pattern with a small, predictable verb set (list, get, add, update). The only wart is the get-vs-list split for reads (get_class_visits, get_client_account_balances sit alongside list_clients, list_sales) and list_bookable_items acting as a finder rather than a plain listing, but these are semantically motivated and readable.

Twenty tools is on the heavy side, but the server spans a wide domain (clients, appointments, classes, schedules, sales, staff, site config), so each tool maps to a distinct API endpoint and resource. Nothing looks redundant or padded for the scope covered.

Read coverage is strong (clients, visits, classes, schedules, services, sales, staff, locations, sites, session types) and core booking flows exist, but there are notable write-side gaps: no cancel/remove appointment, no removal of a client from a class (explicitly punted to the front desk), and no way to create or edit class schedules, classes, or process checkout sales. These dead ends will block cleanup and checkout workflows for an agent.