MCP Tools DirectoryAbout this integration
Relays messages between two Claude Code sessions on different machines using the Channels API
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 2.1.0
- Package
- claude-intercom
- Last compatibility test
- Not independently tested
Connect your agent
claude-intercomThe publisher warns that authenticated peers can inject text into a live session, documents no replay protection, and recommends a private network or TLS tunnel. No messages were sent during review.
Capabilities: Send messages between live Claude Code sessions, Track delivery and reply state, Receive channel notifications over a peer HTTP bridge
Connected profiles
Additional details
io.github.MuhammadTalhaMT/intercom
Source ↗ · Checked 2026-09-172.1.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17MY_ROLE, REMOTE_HOST, INTERCOM_SECRET
Source ↗ · Checked 2026-09-17claude-intercom
Source ↗ · Checked 2026-09-192.1.0
Source ↗ · Checked 2026-09-19Each peer runs a persistent listener, forwards inbound messages into its live session, and tracks sent, delivered-to-process, and answered states.
Source ↗ · Checked 2026-09-19Both peers require the same strong INTERCOM_SECRET; the remote message endpoint checks it in an X-Intercom-Secret header while the health endpoint remains unauthenticated.
Source ↗ · Checked 2026-09-19Claude Code spawns the package as an MCP subprocess over stdio, and the two subprocesses communicate through configured HTTP peer addresses.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19