Log inSubmit server
Agent Comm logo

Agent Comm

Coordinates AI agents through MCP with messaging, channels, shared state, discovery, and real-time events.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Agent Comm

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "agent-comm": {
      "command": "npx",
      "args": [
        "agent-comm"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The agent-comm MCP server connects AI coding agents through direct messages, channels, shared state, and presence tracking. It runs as a Node.js stdio MCP server backed by SQLite, with REST and WebSocket interfaces for hooks, dashboards, and custom clients. Agents can register, discover peers, exchange threaded or broadcast messages, poll for incoming work, and coordinate shared values with atomic compare-and-set operations. Reach for it when multiple agents work on the same codebase and need a common coordination layer.

Use cases

  • Register agents by capability for task routing
  • Send threaded messages between coding agents
  • Coordinate work through shared key-value state
  • Manage channels for project-specific discussions
  • Poll for peer updates without busy-looping

Key features

  • Direct, channel, broadcast, reply, and forwarded messaging
  • Agent registration, discovery, heartbeat, and status
  • Inbox filtering and blocking message polling
  • Channel membership and message history
  • Shared key-value state with atomic CAS
  • SQLite persistence with REST and WebSocket access

Tools7

What Agent Comm lets your agent do. Expand a tool for its parameters.

Self-reported~174 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 48d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · agent-comm (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars9Stargazers on the source repository.
npm downloads945Package downloads in the last 30 days.
Last commit24d agoMost recent push to the default branch.
Tools exposed7Callable tools this server registers over MCP.

How Agent Comm works

What agent-comm MCP server does

The agent-comm MCP server provides a shared coordination service for multiple AI agents working concurrently. Each agent can register an identity with capabilities, metadata, and skills, then discover other registered agents by capability or tag. Registration can also include channels to join automatically.

Communication supports direct recipients, channels, broadcasts, replies, and forwarded messages. Messages can carry importance levels from low through urgent, and inbox queries can filter by unread state or importance. Thread views use a thread identifier to collect related messages.

The service also supplies a shared key-value store. Agents can set, retrieve, list, and delete values, or use compare-and-set for atomic updates. This supports coordination data such as locks, flags, and progress markers without requiring every agent to maintain a separate copy.

How it works

The agent-comm MCP server runs as one Node.js process and exposes MCP over standard input and output for AI hosts. The same process can provide REST endpoints and WebSocket events for scripts, hooks, and the web dashboard. Its persistent data is stored in SQLite using WAL mode, allowing multiple connected hosts to work with the same agents, messages, channels, and state.

The seven MCP tools group the main operations by concern:

  • comm_register creates an agent identity and optionally joins channels.
  • comm_agents lists, discovers, identifies, heartbeats, checks, or unregisters agents.
  • comm_send delivers direct, channel, broadcast, reply, or forwarded messages.
  • comm_inbox reads messages, including filtered and threaded views.
  • comm_poll waits for a new inbox message, with timeout and importance filters.
  • comm_channel manages channel membership, metadata, archiving, and history.
  • comm_state manages shared values, including atomic CAS updates.

A browser dashboard is available at the local server address and presents agents, messages, channels, shared-state entries, and activity in real time. The project also includes optional hooks that use REST calls to coordinate file edits and guard selected shell operations; those hooks are separate from the MCP tool calls.

Setup and configuration

Install the published package globally with npm install -g agent-comm, then add a stdio MCP entry that runs npx agent-comm. A generic configuration uses agent-comm as the server name, npx as the command, and agent-comm as its argument. The dashboard starts at http://localhost:3421 after the first MCP connection.

For a source installation, clone the repository, install dependencies, and run the build. The standalone process can be started with node dist/server.js --port 3421 for REST or WebSocket clients. The repository also provides npm run setup for Claude Code; this registers the MCP server, installs the supplied hooks, and configures permissions.

Host configuration paths vary. Cursor is identified as read-only for state in the tested-host list. Hosts need MCP support for the stdio option, while custom clients can use HTTP interfaces.

Limitations and notes

The server requires Node.js 20.11 or newer. MCP access uses stdio, while REST and WebSocket access is intended for standalone clients, hooks, dashboards, or custom scripts. The supplied coordination hooks can block conflicting edits or selected commands, but they must be installed separately; the MCP primitives alone do not enforce that an agent follows a coordination procedure.

The file-coordination behavior depends on the REST service being available on the configured local port. Review those recipes before relying on hooks in a particular development environment.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Agent Comm

agent-comm is an MCP server that connects AI coding agents through shared messaging, channels, agent discovery, and key-value state. Its main tools register and manage agents, send and read messages, poll inboxes, manage channels, and perform shared-state operations including atomic compare-and-set updates.

Install it with `npm install -g agent-comm`, then configure an MCP host to run `npx agent-comm`. You can also clone the repository, install dependencies, and build it from source. The project documents a separate `npm run setup` path for Claude Code.

In the compatible-client list here, those names map to Claude Code, Cline, Cursor, Windsurf, Codex, and Continue.

Yes, when its optional file-coordination hooks are installed. The `file-coord` hook uses the REST API to claim files and can block an edit when another agent holds the lock. The MCP state tools themselves provide coordination primitives but do not enforce their use.

Yes, the standalone server exposes REST endpoints alongside WebSocket access. These interfaces support hooks, dashboards, and custom scripts, while MCP-compatible AI hosts connect through the stdio transport.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAgent Comm AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/agent-comm?style=directory)](https://allmcps.com/mcp/agent-comm)
HTML Embed
<a href="https://allmcps.com/mcp/agent-comm"><img src="https://allmcps.com/api/badge/agent-comm?style=directory" alt="Agent Comm on AllMCPs" /></a>