No user-submitted related servers found.
Scored across 22 tools
Most tools are cleanly split into read-only resource tools and their mutating counterparts (inbox/answer_inbox, contacts/update_contact, campaign/campaign_status), and descriptions explicitly cross-reference the intended tool. Some overlap remains around replying/sending (answer_inbox vs send_message), reply checking (inbox vs check_replies), and status/reporting (show_status, analytics, campaign_status, suggest_next_action), so an agent could still misselect.
All names are snake_case, with a predictable pattern of resource nouns (contacts, accounts, campaign) paired with action verbs (create_campaign, update_contact, send_message). Minor inconsistencies exist, such as singular/plural pairs (account/accounts, prospect/prospect_view) and noun-only names alongside verb-led names, but nothing chaotic.
22 tools is on the heavy side for a single MCP server and reflects a broad product surface; many operations are bundled into action-parameterized mega-tools. It is borderline rather than excessive, but the count increases the chance of overlapping choices.
The set covers the main outreach lifecycle: setup, accounts, ICP generation, campaign creation/editing/control, contacts, prospects, scheduler, inbox/replies, messaging, analytics, and meeting booking. Minor gaps remain, such as no direct contact creation/import or explicit campaign listing/calendar-connection tool, but core workflows are represented.