Neon CRM MCP by usefulapi

Most tools target a distinct resource and action, so selection is usually clear. However neon_list_accounts vs neon_search and nested list endpoints (e.g., neon_list_account_donations vs neon_get_donation) require careful reading to distinguish, leaving minor ambiguity.

All tools use the neon_ prefix and snake_case with verb-first names, creating a predictable pattern. The only minor deviation is neon_search, which omits an explicit noun/object in the name.

22 tools is slightly above the ideal 3-15 range, but the breadth reflects a multi-entity CRM covering accounts, activities, donations, events, memberships, and campaigns. Each tool appears to earn its place, though a few list/get pairs could potentially be consolidated.

Accounts and activities have create/get/list/update coverage, and search covers multiple resources. However donations, events, memberships, and campaigns lack create/update/delete operations, so agents cannot perform core write workflows such as recording a donation or registering for an event.