Connect Intercom to Claude Code

Let Claude draft replies, tag, and clear the queue in Intercom. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Intercom to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Intercom, you add a Intercom MCP server: a small hosted service that exposes Intercom's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Intercom account. No API keys pasted into config files.

claude mcp add --transport http intercom https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Intercom once connected?

Full read-write Intercom access lets Claude draft a reply inside the live conversation, apply tags, assign to the right teammate, snooze or close a ticket, and update a help center article, all once you approve. The triage and answering that meant tab-switching now happen where the conversation already lives.

Draft a reply inside an existing conversation, preserving the customer and context
Apply or remove tags to triage an inbox
Assign a conversation to a teammate or team
Snooze, reopen, or close a ticket as you clear the queue
Update or create a help center article from a resolved thread
Send a drafted reply after you approve it

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Intercom access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Intercom API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Intercom changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Intercom connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Intercom connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Intercom account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Intercom's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Intercom?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Intercom account it signs in with. Revoking access is one click in Intercom.

More on the Intercom connector

Intercom connector for claude.ai Zendesk + Claude Code Freshdesk + Claude Code Help Scout + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us