Wild Apricot MCP by usefulapi

Every tool targets a clearly distinct resource and action: list vs get vs create/update for contacts, events, registrations, invoices, payments, and saved searches. No two tools appear interchangeable, and descriptions clarify subtle boundaries such as running a saved search vs listing saved search definitions.

All tool names use the same wildapricot_ prefix and a consistent snake_case verb_noun pattern (create_contact, get_event, list_invoices, update_contact, check_in_attendee). The convention is predictable and readable throughout.

Twenty-one tools is on the heavier side but justified by the broad Wild Apricot domain spanning contacts, events, registrations, finances, groups, and saved searches. Each tool maps to a distinct resource/action, so there is little redundancy despite the count.

Core contact and event-registration workflows are covered, but several resource lifecycles are incomplete: there is no delete contact, no create/update/delete for events, and invoices, payments, and donations are read-only. These gaps limit full domain management, though common read and registration tasks can still be performed.