No user-submitted related servers found.
Scored across 22 tools
Every tool targets a distinct resource+action pairing, even within messaging (inbox, ack, await_reply, reply, send_message) and memory (create_memory, read_memory, search_memories vs. put_note, get_note). Descriptions explicitly distinguish overlapping-sounding tools, preventing misselection.
All names use snake_case, but many deviate from a strict verb_noun pattern (inbox, ack, reply, handoff, whoami, session_digest, files_touched). The mix is readable yet not consistently predictable.
22 tools is on the heavy side for a single MCP server. The multi-agent orchestration domain is complex, but the count falls into the borderline 16-25 range that typically feels heavy and may benefit from consolidation.
Core workflows are well covered: messaging, session lifecycle, memory, notes, transcripts, and learning state. Minor gaps exist, such as no delete/update for first-party memory (create_memory errors if the file exists) and no explicit list for notes or memories, but these are workaroundable.