Skill
Agent Comm Hub
多智能体消息转发与上下文共享中间件 — 基于 MCP 协议实现 agent 间通信与任务协同。支持多 Agent 接入，提供标准 MCP 工具接口和本地 SQLite 存储。
When to use Agent Comm Hub
Choose if
You're building a multi-agent system and need a shared MCP-protocol bus for agent-to-agent messaging, task handoff, parallel task groups, and context sharing — backed by local SQLite with <50ms latency and 53 MCP tools spanning identity, messaging, files, tasks, context, orchestration, and ops. Useful when independent agents must coordinate without a hosted broker.
Avoid if
You only have one agent — the middleware is overkill. You need cloud-hosted multi-tenant messaging (this is local SQLite). You need fully unattended automation — the README requires user confirmation for 10 high-risk operations. File attachments above 10MB must use a different channel.
Risk Flags
- MEDIUM auth Server requires a `HUB_KEY` authentication token for stdio mode. README documents the env var; agents without the key cannot connect.
- MEDIUM rate_limit README states a 10MB per-attachment cap, 1–500 messages per batch ack, 2–10 tasks per parallel group, 30s heartbeat with 90s+ offline marker, and 3 retries with 100ms→200ms→400ms exponential backoff.
- MEDIUM scope README requires user confirmation for 10 high-risk operations (broadcasts, task assignment, batch acknowledgment, pipeline creation, quality gates, data archival, etc.) — not safe for fully unattended use.
- LOW runtime Server requires Node.js 18+, @modelcontextprotocol/sdk ^1.10.2, express ^4.19, better-sqlite3 ^11.9, zod ^3.23. Client requires Python 3.9+ standard library only.
Cost
Type: Free
Dependencies
Minimum runtime: Node.js 18+ (server); Python 3.9+ (client)
Distribution
- ClawHub
liubo-agent-comm-hub- License
- MIT-0