No user-submitted related servers found.
Scored across 38 tools
Most tools target clearly distinct resources or actions, and the descriptions explicitly route between similar surfaces such as send_message vs broadcast vs post_to_channel vs post_task, and get_messages vs get_messages_summary vs peek_inbox_version. A few messaging and task lanes still overlap enough that an agent must read the long descriptions to choose correctly.
Nearly all names use snake_case and most are verb-first, making the set predictable. Minor deviations exist, including task_schema_get (noun-first), health_check, whoami, broadcast, and prepositional post_to_* names mixed with post_task.
The server exposes 38 tools, far above the typical 3-15 range, and the surface includes many niche admin, token, schema, dashboard, and lifecycle operations. The domain is broad, but the tool count feels heavy and fragmented rather than tightly scoped.
Core messaging, task, agent, webhook, and token lifecycles are covered, but there are notable gaps: no list_channels or delete_channel, no list_task_schemas, no get_dashboard_theme, and no single-message lookup or search. Some gaps are workaroundable, but channel and schema discovery are meaningful omissions for the apparent domain.