Agent Comm Hub

This Skill addresses the pain points of real-time bidirectional communication and context synchronization between multiple AI agents. In practical development, developers often need multiple independent AI agents (e.g., Hermes, WorkBuddy) to collaborate, but the lack of a unified communication protocol and message persistence mechanism leads to fragmented tasks and lost context. Agent Comm Hub provides 58 structured tools via the MCP protocol (stdio / HTTP-SSE), centralizing message forwarding, task assignment, shared memory, and an evolution engine into a single Hub with latency under 50ms, enabling agents to collaborate as efficiently as a human team.

Usage is straightforward: you simply start the Hub server locally (supporting stdio mode or HTTP-SSE mode) and connect via an MCP client. You can then use natural language instructions to register Agents, send peer-to-peer messages, create tasks, stage context, query online status, and more. For example, tell your AI assistant: "Help me start the Agent Communication Hub, register an Agent named WorkerA, then send a message 'Please process order #123' to WorkerB, and check if it's delivered." The Hub will automatically invoke tools like get_online_agents, register_agent, and send_message to complete communication link verification and message delivery. The entire process, from zero to the first inter-agent communication, can be completed within 5 minutes.

It is well-suited for teams or individuals requiring multi-agent collaboration, especially developers already using multiple AI coding agents (e.g., Claude, Cursor, Trae) for development who wish to have them share task status, exchange intermediate results, and centrally manage context. It is also suitable for academic researchers studying multi-agent systems and project managers needing to orchestrate sub-agents for complex workflows. Whether you're building automated pipelines, customer service bot clusters, or experimenting with emergent multi-agent behaviors, this Hub provides reliable infrastructure.

It is recommended to use this Hub in a local development environment or internal network to ensure communication latency and security. Note that it primarily uses SQLite WAL for message persistence, making it suitable for single-machine or small-scale deployments; it does not support cross-network distributed clusters. All Agents must connect to the same Hub instance. Registering a new Agent requires an invite_code, which should be prepared in advance. Additionally, Agents must send a heartbeat every 30 seconds to maintain online status; absence of a heartbeat for over 90 seconds will automatically mark them as offline.