Home › Other › claude-intercom

claude-intercom

Relays messages between two Claude Code sessions on different machines using the Channels API

TypeScript

★ 20 stars Last pushed 2026-08-19 License: MIT

View repository →

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 claude-intercom@2.1.0

Or add to your MCP client config:

{
  "mcpServers": {
    "claude-intercom": {
      "command": "npx",
      "args": [
        "-y",
        "claude-intercom@2.1.0"
      ],
      "env": {
        "MY_ROLE": "<YOUR_VALUE>",
        "REMOTE_HOST": "<YOUR_VALUE>",
        "INTERCOM_SECRET": "<YOUR_VALUE>",
        "INTERCOM_PORT": "<YOUR_VALUE>",
        "INTERCOM_HOST": "<YOUR_VALUE>",
        "INTERCOM_SEND_TIMEOUT_MS": "<YOUR_VALUE>"
      }
    }
  }
}

MY_ROLE required — Label for this instance, e.g. backend or frontend. Appears in message tags so the other side knows who is talking.
REMOTE_HOST required — Address of the other machine as host:port. A Tailscale address is recommended over a public one.
INTERCOM_SECRET required 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.