No user-submitted related servers found.
Scored across 14 tools
Most tools target clearly distinct actions: hub_ask vs hub_answer (question vs response), hub_send vs hub_inbox vs hub_history are separated by the descriptions' read-semantics. The only real overlaps are hub_role/hub_process (both about how the crew/role works) and the read-message pair, which descriptions largely disambiguate.
Every tool uses a consistent 'hub_' prefix with a single lowercase token, so the surface is predictable at a glance. However, the trailing tokens mix verbs (ask, answer, send, rename) with nouns (inbox, history, agents, task), so the resource+action shape isn't uniform.
14 tools sits squarely in the well-scoped range, and each one maps to a distinct facet of multi-agent chat coordination (messaging, tasks, presence, identity, linking). Nothing appears redundant at the count level.
The chat/coordination domain is well covered: messaging, read state, task lifecycle (add/take/assign/update/lease/return), presence, identity, files, and session linking. Minor gaps remain, such as no message search or explicit leave/remove operations, but core workflows have no dead ends.