Agent Comms MCP Server

Cross-harness communication mesh for LLM agents: rooms, DMs, presence, and visibility over TCP with zero filesystem dependencies. It runs locally over stdio via the published package.

People who work with communication, mesh and presence and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-09-18 · ★ 20 · #43 OF 945 MAINTAINED OTHER · VERIFIED 2026-09-18

TypeScript servers · how we verify → /methodology

01 · Install Agent Comms

Claude Code

claude mcp add exadev-agent-comms -- npx -y agent-comms

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "exadev-agent-comms": {
      "command": "npx",
      "args": [
        "-y",
        "agent-comms"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license no standard license detected - usage rights unclear; check the repo before commercial use

npm package agent-comms - unscoped; check the name against the project README before installing

registry namespace io.github.ExaDev is GitHub-verified and matches the repo owner

03 · What Agent Comms can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v3.15.0 · 2026-09-18

3.15.0 (2026-09-18) · let GatewayTrust load and persist its allowlist per bridge slot · persist a slot's trusted-gateway device-id set · thread the identity slot through to MeshStore's gatewayTrust

v3.14.0 · 2026-09-17

3.14.0 (2026-09-17) · route hub-relayed requests to the correct local peer via toDevice · bump wire-mesh-core to 1.48.2 (0d23e12), references wire-mesh#175

v3.13.0 · 2026-09-17

3.13.0 (2026-09-17) · add GatewayTrust, the cross-machine gateway allowlist · expose gateway trust as gateway_trust/gateway_untrust/gateway_list_trusted tool actions · gate hub gossip forwarding on gateway trust · gate…

04 · Who maintains Agent Comms

Agent Comms is maintained by exadev. It's the only MCP server we track from this author; the repo dates to Apr 2026.

05 · Facts

repository: github.com/exadev/agent-comms
category: other - ranked #43 of 945 actively-maintained other servers as of 2026-09-18.
release cadence: 10+ releases in the last 90 days (latest 2026-09-18)
registry: io.github.ExaDev/agent-comms (active, first published 2026-05-21 · 121 versions)
packages: npm:agent-comms

06 · Agent Comms FAQ

What is Agent Comms?

Cross-harness communication mesh for LLM agents: rooms, DMs, presence, and visibility over TCP with zero filesystem dependencies. It runs locally over stdio via the published package.

Is Agent Comms still maintained?

Yes - as of 2026-09-18, its last commit was 2026-09-18 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

How do I install Agent Comms?

Run `npx -y agent-comms`. You can also paste the ready-made client config above.

Does Agent Comms run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Agent Comms

Alternatives to Agent Comms

Maintained other servers if Agent Comms isn't the fit.

More MCP servers to compare · MNE MCP · Explorium · Nuxt I18n MCP · Workix · Harmonyos

More TypeScript MCP servers · Ordinals · Yieldagentx402 · see all