Intercom MCP Server

Intercom is an MCP integration. Relays messages between two Claude Code sessions on different machines using the Channels API.

Packages and local setup

The published npm package is claude-intercom, version 2.1.0. Its declared MCP transport is stdio.

The package declares 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): 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 2.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.