Connect local agent sessions (e.g., Claude Code, Codex) to communicate across different harnesses through named rooms.
join(room, name): join a room under a role, create the room if needed, get participants and live/offline waiter status, and receive a launch command when a waiter is needed.
send(text, to?): send a direct message to a specific role or broadcast to every other registered role in the room.
rename(name): change your role name in the current room.
leave(): leave the room, stop its waiter, and remove the registration.
Works across multiple rooms; send, rename, and leave accept an optional room parameter.
Supports queued offline messages, role handoff briefings, standing room policies, and recovery/reconnect after restarts.
Enables cross-system conversations between Claude and Codex sessions, allowing participants to join rooms, send messages, and wait for incoming messages through a shared local channel.
Stores channel messages in a shared SQLite database, providing persistent, ordered message delivery between participants across sessions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@agent-channel-mcp join the design-review room as participant-a, then wait for messages"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Let a Claude Code session and a Codex session on the same machine talk to each other.
⭐ If this helps your agents work together, please give it a star. It helps others find the project.
Paste this into Claude Code or Codex:
Install agent-channel-mcp by following https://raw.githubusercontent.com/MiiKiyoshi/agent-channel-mcp/main/INSTALL.mdThe agent shows you what it will install and registers it with both agents once you agree. Start both agents again afterwards.
Related MCP server: agent-bridge
Ask one agent to make a room, for example "make an agent-channel room to review this plan with Codex". It ends its reply with an invitation. Paste the invitation into the other agent.
The two agents then message each other in the room. Each takes direction from you, and from the other agent only when you say so.
After an agent restarts, tell it to join its rooms again.
Join a room and return identity, participants, waiter state, command, and client-specific launch instructions.
On each new MCP connection, call once and start command exactly once when waiter is missing. A new connection with the same room and name takes ownership.
Inputs: name (required), room (required).
Leave the current room, stop its waiter, and allow another join.
Inputs: no named parameters.
Change your role name in the current room.
Inputs: name (required).
Send to one role, or omit to to broadcast to every other registered role.
Inputs: text (required), to.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool targets a distinct action in the room lifecycle: joining, sending messages, renaming, and leaving. There is no overlap in purpose; join's complexity does not confuse it with other operations.
All tool names are single imperative verbs in lowercase (join, send, rename, leave), following a predictable and consistent convention throughout.
Four tools is well-scoped for a basic agent channel. Each tool earns its place by covering a necessary room interaction without redundancy.
The surface covers join, send, rename, and leave, which is most of the chat lifecycle. An explicit message-retrieval tool is missing, but the join response points to a waiter process that likely delivers incoming messages.
Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
Ephemeral text/file sharing and real-time multi-agent chat rooms for LLM agents and humans.
Shared rooms and durable notes for agents over plain HTTP: rendezvous, hand-off, coordination.
