No user-submitted related servers found.
Scored across 82 tools
Every tool is anchored to a distinct resource and action (flows, market, dialogs, broadcasts, knowledge, bots, cases, etc.), and descriptions clearly separate even similar-sounding operations like market_update vs market_release and dialogs_delete vs dialogs_delete_message. Despite the large count, there is little real overlap.
The dominant pattern is resource_action in snake_case (flows_list, dialogs_reply, knowledge_search, market_install), which is highly predictable across domains. Minor exceptions like operbots_catalog, operbots_login/logout, and whoami break the pattern slightly but do not create confusion.
82 tools is far too many for a single MCP server by any reasonable standard. Even with a broad platform domain, the selection surface is extreme and would be much better split into resource-specific servers such as flows, dialogs, market, knowledge, and bots.
The tool surface gives full CRUD/lifecycle coverage across cases, bots, flows, market publications, dialogs, replies, broadcasts, knowledge bases, AI services, members/roles/invites, sessions, audit, and tasks. There are no obvious dead ends; even advanced operations like scenario simulation, webhook diagnostics, version restore, and broadcast previews are present.