claude-code-relay
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
claude-code-relay
Relay messages between Claude Code sessions over MCP — without stealing window focus.
Run several Claude Code sessions in parallel and let them message each other. A message
is injected into the target session's conversation in the background, as a <channel>
block — no keystroke paste, no window jumping to the foreground. You keep typing where you
are; the message just appears in the other session.
The problem
If you drive multiple Claude Code sessions at once, you eventually want them to talk — one hands work to another, or asks a question. The obvious way (paste into the target terminal) steals focus: the target window jumps to the front and your next keystrokes land in the wrong place. That makes genuine parallel work painful.
Related MCP server: peer-relay
The approach
claude-code-relay uses Claude Code's experimental channel capability. Each session
runs a tiny MCP server that:
listens on a local HTTP port, and
pushes any received message into its own conversation via the
notifications/claude/channelnotification.
Delivery is a plain HTTP POST from the sender to the receiver's port. Background injection means the receive is focus-free.
session "alice" session "bob"
send.js ──HTTP POST 127.0.0.1:8802──▶ channel.mjs (MCP server)
│
▼ notifications/claude/channel
<channel source="claude-code-relay" from="alice">
hey, can you take the migration?
</channel> ← appears in bob's conversationQuick start
npm install
cp ports.example.json ports.json # map session names -> portsRegister the receiver per project in .mcp.json, giving each session its own port via
RELAY_CHANNEL_PORT:
{
"mcpServers": {
"claude-code-relay": {
"command": "node",
"args": ["./channel.mjs"],
"env": { "RELAY_CHANNEL_PORT": "8801" }
}
}
}Launch each Claude Code session with development channels enabled (experimental flag), on its own port:
RELAY_CHANNEL_PORT=8801 claude --dangerously-load-development-channels # session "alice"
RELAY_CHANNEL_PORT=8802 claude --dangerously-load-development-channels # session "bob"Send a message from one session to another:
node send.js alice bob "hey, can you take the migration?"It shows up in bob's conversation as a <channel> block. Bob replies the same way:
node send.js bob alice "on it"Notes & caveats
Experimental flag. This relies on Claude Code's
--dangerously-load-development-channelsand theclaude/channelcapability. Both are experimental and may change between releases.Receive-only channel. The channel only delivers into a session; there is no reply tool. Sessions reply by running
send.js. Typing in the window sends nothing.Localhost only. Servers bind
127.0.0.1— this coordinates sessions on one machine.ASCII session names are recommended (the sender name travels in an HTTP header).
One port per session. A duplicate spawn on a taken port exits cleanly (no churn).
Verify it works
mcp-probe.mjs starts the receiver as a real MCP server (over stdio, exactly as Claude Code would), sends a message over HTTP, and asserts it comes back as a notifications/claude/channel notification — the full injection path, end to end:
npm test
# -> E2E PASS: HTTP POST -> channel.mjs -> notifications/claude/channel -> MCP clientThe only thing this can't assert headlessly is the final UI render, which is Claude Code's job.
License
MIT © TEAM ROCK
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA transparent message ferry between Claude Desktop and Claude Code CLI, enabling task delegation with any MCP configuration without the bridge needing to know about specific MCPs.1MIT
- AlicenseNot gradedqualityDmaintenanceA message relay MCP server enabling two separate Claude Code instances to exchange direct questions and answers asynchronously without sharing context.MIT
- AlicenseAqualityCmaintenanceEnables real-time cross-machine communication for Claude Code agents using a shared MCP relay server.13291 PyPI15MIT
- AlicenseAqualityFmaintenanceMCP server that routes Claude Desktop chat into Claude Code, enabling headless execution and terminal handoff with session continuity.4MIT