No user-submitted related servers found.
Scored across 41 tools
Most tools target a distinct resource or lifecycle action, and descriptions explicitly contrast easily confused pairs such as open_obligations vs ready_work vs awaiting_ack, and read_inbox vs list_messages vs search_messages. A few listing/status tools still overlap conceptually, but the boundaries are generally clear.
The set is consistently snake_case and overwhelmingly verb-led (send_message, resolve_message, pin_set, upload_content). Some tools use noun/adjective-led names such as awaiting_ack, channel_status, server_build, and board_link, which are readable but deviate from a strict verb_noun pattern.
At 41 tools, the surface is very heavy for an agent-facing MCP server, mixing core messaging with admin, informational, migration, and edge-case lifecycle tools. The domain is complex, but the count is well above a well-scoped range and increases selection burden.
The tool set covers the channel domain comprehensively: messaging, replies/threads, unread tracking, obligations, resolutions, acknowledgements, work status transitions, pins, uploads, role/channel administration, waiting, and backfill/undo. No obvious core workflow dead ends are apparent.