Agent Comm
Give multiple agents or workflows a shared messaging layer with channels, state, and live events over stdio MCP.
Overview
agent-comm is a MCP server for the Build phase that provides messaging, channels, shared state, and real-time events between AI agents over stdio.
What is this MCP server?
- Messaging and channels for agent-to-agent coordination
- Shared state and real-time events across agent sessions
- stdio npm package agent-comm for local MCP wiring
- GitHub source keshrath/agent-comm at registry version 1.3.9
- Fits multi-agent local dev without building a custom message bus
- Package version 1.3.9
- Transport: stdio
- Registry: npm identifier agent-comm
Community signal: 4 GitHub stars.
What problem does it solve?
Your multi-agent setup cannot coordinate without bespoke scripts and fragile file-based handoffs.
Who is it for?
Builders experimenting with multi-agent local setups who want stdio MCP messaging without standing up Redis or Slack bots.
Skip if: Production-scale team chat, compliance-heavy audit trails, or single-agent workflows that need no coordination.
What do I get? / Deliverables
Agents share channels, state, and live events through one MCP server so parallel workflows stay in sync locally.
- MCP-accessible messaging and channels between agents
- Shared state and event subscriptions for coordinated tasks
- Less custom glue code for local agent orchestration
Recommended MCP Servers
Journey fit
Inter-agent communication is infrastructure you add while assembling agent stacks, which maps to Build agent-tooling. Agent-tooling covers MCP servers that coordinate how coding agents and sidecar processes talk to each other.
How it compares
Agent coordination MCP over stdio, not a hosted team chat integration or API test runner.
Common Questions / FAQ
Who is agent-comm for?
Indie developers and small teams wiring multiple MCP-aware agents on one machine who need channels, shared state, and events.
When should I use agent-comm?
Use it during Build when you split work across agents and need structured messaging instead of manual copy-paste between sessions.
How do I add agent-comm to my agent?
Add the npm MCP package agent-comm (v1.3.9) with stdio transport in your client config per the keshrath/agent-comm repository.