Intercom MCP server

Claude Intercom

Two-way communication bridge between Claude Code sessions using the Channels API.

Let two Claude Code instances on different machines talk to each other in real-time. One sends a message, the other receives it instantly as a channel notification and can reply back.

What Intercom does that native can't

Claude Code has native cross-session messaging now. Here's where Intercom is still the answer:

• Two different people. This is the big one. Native connects your sessions — the inbox is tied to your own OS user and cross-machine delivery rides your own Remote Control. A backend dev on their laptop and a frontend dev on theirs are two accounts, and native can't join them. That two-person hotline is exactly what Intercom was built for.
• Native Windows. Native messaging is macOS and Linux only. Intercom is Bun over HTTP and doesn't care what OS you run.
• Your network, not Anthropic's. Native cross-machine messages relay through Anthropic servers. Intercom POSTs straight over your own network, VPN or tunnel.
• Any provider. Works on Bedrock, Vertex and Foundry, and in telemetry-disabled environments, where native messaging is switched off.
• Container to host. Native discovery works through files on disk, so a session in a container and one on the host can't see each other. Intercom just needs a reachable port.
• Honest delivery. sendmessage reports sent, delivered-to-process and answered as three separate states, plus a checkmessage tool. You find out when the other side never picked it up, instead of planning around an answer that was never coming.

If you're on macOS or Linux and you just want your own sessions talking to each other, native is simpler — use that. Everything else above is what this is for.

Why?

If you have a backend developer and a frontend developer each running Claude Code on separate machines, they currently have to relay questions through Slack/Discord/copy-paste. Claude Intercom creates a direct hotline between the two AI sessions — one Claude can ask the other about endpoints, schemas, or implementation details and get answers from the actual codebase.

Architecture

Machine A                          Machine B
(e.g. backend dev)                 (e.g. frontend dev)

Claude Code A                      Claude Code B
     |                                  |
     +-- intercom.ts ---HTTP POST----> intercom.ts --+
     |   (channel)     <--HTTP POST--  (channel)     |
     |                                               |
     +-- stdio (MCP) --+        +-- stdio (MCP) -----+
                        |        |
                   Claude A    Claude B

Both instances run the same intercom.ts file. Each listens for HTTP messages and pushes them into its local Claude Code session via the Channels API. Each also exposes sendmessage and checkmessage tools that Claude can call.

Requirements

• Claude Code v2.1.80 or later
• Bun runtime
• Both machines must be able to reach each other over HTTP. Tailscale is the recommended way — see Connecting the two machines

Set it up with Claude

Paste this into a Claude Code session on each machine and it will walk you through the whole thing. Run it on machine A first, keep the secret it gives you, then run it on machine B.

Set up claude-intercom on this machine so this Claude Code session can message
a Claude Code session on my other machine.

Work through this in order, and stop and ask me whenever you need something
only I can tell you.

Shortened. The full README is on GitHub.