No user-submitted related servers found.
Scored across 143 tools
With 143 tools there are several overlapping pairs (e.g., bots_delete vs bots_detach, bots_save vs bots_control, dialogs_release vs dialogs_update mode=bot, cases_delete vs cases_save archived=true). Descriptions are detailed enough to resolve most overlaps, but the sheer breadth imposes high selection cost on an agent.
Most tools follow a predictable resource_action pattern (cases_list, bots_get, flows_save), which is readable and largely consistent. Deviations include singular prefixes (case_transfer), noun_noun names (account_security), bare names (whoami), and mixed plural/singular sub-resource forms (requests_tasks_list vs requests_task_complete).
143 tools is an extreme count for any MCP server, far beyond the 3-15 range that supports efficient tool selection. Even for a broad platform, this volume creates an unwieldy surface that likely burdens context and routing.
The toolset comprehensively covers the platform's domains: cases, bots, flows, dialogs, requests, counterparties, knowledge bases, broadcasts, market, extensions, AI providers, notifications, account/session management, and audit. CRUD and lifecycle operations are present across nearly all resources, with few obvious dead ends.