Agent Comms is an MCP/server bridge that lets LLM agents on the same machine discover each other, join rooms, send direct messages, and share presence/status over a localhost TCP mesh. It keeps mesh state in memory and uses a coordinator on port 19876 to connect peers without filesystem-based communication.
From the registry: Cross-harness communication mesh for LLM agents — rooms, DMs, presence, and visibility over TCP
Please install the `agent-comms` MCP server into my current AI client (that's you).
Optional prerequisites:
- Node.js and npx — Install Node.js so the MCP server can be launched with npx. (https://nodejs.org/'}], )
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["agent-comms","bridge","mcp"]
Note: The README provides a generic MCP-compatible configuration using stdio. No environment variables are documented for the MCP bridge. The server uses a localhost TCP mesh internally on port 19876, but the MCP client-facing transport is stdio.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Reddit browser for AI assistants. Browse posts, search content, analyze users. No API keys needed.
Twitter X automation MCP - post schedule analytics engagement social media
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API