Virtuous MCP by usefulapi

Most tools map to a distinct resource+action, but the contact lookup surface has three overlapping entry points (virtuous_find_contact, virtuous_search_contacts, and virtuous_search / virtuous_query), and agents may misselect which to use. The descriptions do disambiguate by scope (exact email/reference vs partial match vs global full-text), so the overlap is manageable rather than fatal.

Every tool follows the same virtuous_<verb>_<noun> snake_case pattern (get_contact, list_contact_gifts, search_projects, create_gift_transaction). Singular/plural and resource ordering are predictable, so an agent can guess a name from intent.

21 tools is on the heavy side, but the server spans several resources (contacts, individuals, gifts, projects, events, tags, notes, queries), and each tool earns its place as a distinct endpoint wrapper. A couple (virtuous_search_contacts vs virtuous_search, virtuous_get_query_options) could be folded without losing capability.

Read coverage is strong and creation is handled via import-pipeline transactions, but there are no update/delete operations anywhere: tags can be applied but not removed, notes created but not edited/deleted, and contacts or gifts cannot be corrected after the fact. Event detail and gift/pledge lifecycle writes are also thin, which will leave agents at dead ends for maintenance workflows.