No user-submitted related servers found.
Scored across 12 tools
Most tools are clearly separated by resource and action: list, search, and get operations target contacts, inboxes, agents, conversations, messages, pipelines, pipeline items, and tasks. The main overlap is between pipeline_get, which can return pipeline items, and pipeline_items_list, though the descriptions clarify the distinction.
Tools consistently use snake_case resource_action naming such as contacts_list, conversations_list, pipeline_get, and tasks_list. There are minor singular/plural deviations (contacts_list/search vs contact_get, pipelines_list vs pipeline_get), but the overall convention is predictable.
Twelve tools is well within the appropriate range for a CRM server and each tool maps to a recognizable read operation. The set is not bloated, though it is notably read-only.
The surface covers many list/get/search operations but lacks any create, update, or delete tools for contacts, conversations, pipeline items, or tasks. For a CRM, this is a significant gap because agents cannot perform common write workflows.