Home › Other › claude-intercom
claude-intercom
Relays messages between two Claude Code sessions on different machines using the Channels API
Connect
Review any command before running it. Package names and URLs come from the server's own registry entry.
Package (npm 2.1.0)
npx -y [email protected]
Or add to your MCP client config:
{
"mcpServers": {
"claude-intercom": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"MY_ROLE": "<YOUR_VALUE>",
"REMOTE_HOST": "<YOUR_VALUE>",
"INTERCOM_SECRET": "<YOUR_VALUE>"
}
}
}
}
MY_ROLErequired — Label for this instance, e.g. backend or frontend. Appears in message tags so the other side knows who is talking.REMOTE_HOSTrequired — Address of the other machine as host:port. A Tailscale address is recommended over a public one.INTERCOM_SECRETrequired secret — Shared secret authenticating messages between the two instances. Must match on both sides. There is no default: without it the intercom starts unpaired, binds no port, and refuses to send.INTERCOM_PORT— Port to listen on for incoming messages. Defaults to 8788.INTERCOM_HOST— Interface to bind the listener to. Defaults to 0.0.0.0. Set 127.0.0.1 when a tunnel fronts the intercom, so only the tunnel can connect.INTERCOM_SEND_TIMEOUT_MS— How long an outbound POST may hang before giving up. Defaults to 10000.
Related servers
REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
browser-use
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
paperclip
Trending hip-hop artist momentum scores across four cultural dimensions.
World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
Ruflo
Agent teams, swarms, memory and hooks for Claude Code and Codex, served over MCP.
Front-End Checklist
Review frontend code and live pages against 386 quality-gated web development rules.
Data from the Official MCP Registry