NexHealth MCP by usefulapi

Each tool targets a clearly distinct resource+action: appointments (book/get/list/update), patients (create/get/search), slots, types, insurance, locations, operatories, procedures, providers, and sync status. The only superficially similar pair — list_appointments vs list_appointment_slots — is distinguished explicitly as existing appointments vs bookable start times, and get_patient vs search_patients differ by id-lookup vs attribute-search.

All tools share the nexhealth_ prefix followed by a consistent verb_noun pattern (book_appointment, create_patient, get_patient, list_*, search_patients, update_appointment). The lone non-verb form sync_status is a well-understood status noun and does not break readability.

16 tools is just over the ideal band but each maps to a distinct endpoint and earns its place in a scheduling/EHR workflow. A large share of read-only list endpoints is justified by the domain's reference-data needs (locations, providers, operaries, types).

The core scheduling loop is well covered (book, list, get, reschedule/cancel, slots plus patient create/get/search and reference lookups). The main gap is patient mutation — no update_patient — and insurance/procedures are read-only, so some post-booking workflows dead-end.