MCP server enabling room-based messaging between multiple agents
Connect Agent Communication MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server enabling room-based messaging between multiple agents. The agent communication mcp mcp server is what makes that connection.
エージェント間のルームベースコミュニケーションを実現するModel Context Protocol (MCP) サーバー
The server ships on npm as agent-communication-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
AGENT_COMM_DATA_DIR — データファイルの保存ディレクトリAGENT_COMM_LOCK_TIMEOUT — ファイルロックのタイムアウト時間（ミリ秒）AGENT_COMM_MAX_MESSAGES — ルームあたりの最大メッセージ数AGENT_COMM_MAX_ROOMS — 最大ルーム数AGENT_COMM_WAIT_TIMEOUT — wait_for_messagesの最大タイムアウト時間（ミリ秒）Configuration is passed through the environment: AGENT_COMM_DATA_DIR. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Agent Communication MCP's toolset — AGENT_COMM_DATA_DIR, AGENT_COMM_LOCK_TIMEOUT, AGENT_COMM_MAX_MESSAGES and 2 more — is a fair guide to whether it matches your workflow. It is maintained by mkXultra; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| AGENT_COMM_DATA_DIR | データファイルの保存ディレクトリ |
| AGENT_COMM_LOCK_TIMEOUT | ファイルロックのタイムアウト時間（ミリ秒） |
| AGENT_COMM_MAX_MESSAGES | ルームあたりの最大メッセージ数 |
| AGENT_COMM_MAX_ROOMS | 最大ルーム数 |
| AGENT_COMM_WAIT_TIMEOUT | wait_for_messagesの最大タイムアウト時間（ミリ秒） |
{
"mcpServers": {
"agent-communication": {
"command": "npx",
"args": ["agent-communication-mcp"],
"env": {
"AGENT_COMM_DATA_DIR": "/path/to/data/directory"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AGENT_COMM_DATA_DIR | Filesystem location the server is allowed to use. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
AI-powered access to Attio CRM. Manage contacts, companies, deals, tasks, and notes. Search records, update pipelines, and automate workflows for
Real availability, real bookings, and single-use scheduling links — driven from the conversation.