agent_communication_clear_room_messages
Clear all messages in a specified room. Requires explicit confirmation to prevent accidental data loss
LABSCO SUMMARY
agent_communication_wait_for_messages is what separates this from a shared log — an idle agent blocks until something is actually said.
Around it the surface is a small, predictable room model: create, enter, leave, list users, send, read. Long-polling is the piece that matters for orchestration, because an agent waiting on a peer's answer costs nothing while the answer does not exist, and the call returns straight away if the message arrived while it was busy elsewhere. State lives wherever AGENT_COMM_DATA_DIR points, which makes the rooms exactly as durable and as shareable as that path is, and agent_communication_clear_room_messages is the one destructive call — it will not run without confirm.
What it is
A message-room server for agents, exposing room creation and membership, message send and read, a long-polling wait, per-room statistics and a guarded reset, with its data held under the directory named in AGENT_COMM_DATA_DIR.
What you get
- Rooms as the unit of conversation: agent_communication_create_room takes roomName and description, agent_communication_list_rooms returns what exists, and agent_communication_list_room_users reports who is inside one.
- Membership under a name: agent_communication_enter_room and agent_communication_leave_room each take agentName and roomName, so a room's participants are explicit.
- Messaging: agent_communication_send_message posts message to roomName as agentName, and agent_communication_get_messages reads history back with limit and before for paging.
- A blocking wait rather than a poll loop: agent_communication_wait_for_messages holds until new messages arrive or timeout is reached, and returns immediately when messages have already landed since the last check.
- Room statistics: agent_communication_get_status reports online users, message counts and storage usage, for one roomName or across the system.
- A guarded reset: agent_communication_clear_room_messages empties a room and requires confirm to be set before it will act.
Requirements
A directory for the server's data, given as AGENT_COMM_DATA_DIR.
Setup effort
One command — npx agent-communication-mcp
USE CASES
01
Handing work from a planner agent to workers and waiting on the result
Join the room under a name, post the task, and block until a worker replies rather than polling for it.
02
Catching up on what a group of agents said to each other
Page back through the room's history, see who was present, and check the volume before reading further.
03
Isolating one task's chatter from everything else in flight
Open a room for the job, bring in the agents that belong to it and no others, and have them leave when their part is done.
04
Resetting a room between runs so old traffic does not confuse the next one
Check what the room is currently holding, then clear its messages with the confirmation the call insists on.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
agent_communication_create_room
Create a new room
agent_communication_enter_room
Enter a room
agent_communication_get_messages
Get messages from a room
agent_communication_get_status
Get system status or specific room status with statistics including online users, message counts, and storage usage
agent_communication_leave_room
Leave a room
agent_communication_list_room_users
List users in a room
agent_communication_list_rooms
List all available rooms
agent_communication_send_message
Send a message to a room
agent_communication_wait_for_messages
Wait for new messages in a room using long-polling. This tool will block until new messages are available or the timeout is reached. Returns immediately if new messages are already available since the last check.
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected.
Requires
- npx on PATH
- AGENT_COMM_DATA_DIR in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"agent-communication": {
"command": "npx",
"args": [
"agent-communication-mcp"
],
"env": {
"AGENT_COMM_DATA_DIR": "<YOUR_AGENT_COMM_DATA_DIR>"
}
}
}
}npx
TERMINAL
npx agent-communication-mcp
