No user-submitted related servers found.
Scored across 105 tools
Most tools have distinct verbs and resource names, and the descriptions are unusually detailed, but the 105-tool surface creates real overlap: list_posts vs list_recent_posts, get_account vs get_overview, update_contact vs upsert_contact, and publish_flow vs activate_flow can be confused. Flow and comment-trigger lifecycle tools are numerous and require careful reading to choose correctly.
Tool names consistently use snake_case verb_noun patterns such as list_contacts, create_flow, publish_post, and cancel_appointment. Minor variations like bulk_approve_comment_replies and get_wins_and_opportunities still fit the convention.
At 105 tools, this is far beyond a practical MCP server scope and fits the rubric's extreme-mismatch range. The breadth spans contacts, conversations, flows, comment triggers, posts, competitors, knowledge, and AI config, creating heavy selection load even though individual tools are purposeful.
Coverage is broad and most domains have full lifecycle support: contacts, appointments, flows, comment triggers, posts, competitors, FAQs, services, and documents. Notable gaps remain, especially media upload for posts despite create_post referencing POST /posts/{id}/media, and there is no mutation tool for AI configuration beyond read-only getters.