Breeze ChMS MCP by usefulapi

Each tool targets a distinct resource and action: list_* tools enumerate collections, get_* tools fetch single records, and the write tools (add_person, assign_tag, record_attendance, etc.) map to unambiguous operations. The get/list pairs (get_event vs list_events, get_person vs list_people) are standard single-vs-collection splits that descriptions clarify. No two tools appear interchangeable.

Every tool uses the same breeze_ prefix followed by a consistent verb_noun snake_case pattern (list_people, get_event, add_tag, update_person, assign_tag, unassign_tag). The assign/unassign pairing is symmetric and predictable. No convention mixing anywhere in the set.

24 tools is on the heavier side but justified by the breadth of the domain (people, events, attendance, volunteers, tags, forms, giving, account). Every tool maps to a real Breeze API endpoint with a clear surface, so none feel redundant. It sits at the upper edge of 'well-scoped' rather than over-stuffed.

Read coverage is thorough, but the write surface is thin: there is no delete for people, tags, or events (event deletion is explicitly unsupported), no update_event, and no way to edit tags or form structures. Create+read+partial-update is present, but missing destructive/update operations create dead ends for lifecycle management.