Skip to main content
Back to the Intercom MCP server

MCP Gateway · Claude Code

Intercom icon

Connect Intercom to Claude Code

Bug reports often arrive as Intercom conversations, with the customer's own description and account details attached. With Intercom behind the Speakeasy MCP Gateway, Claude Code can read the conversation and the contact's profile while it reproduces the problem locally. Agent hooks check each prompt and tool call before Claude Code runs it.

Category
Communication
Tools
13
Authentication
OAuth
Claude Code
CLI

Behind the MCP Gateway

Run Intercom MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Intercom call inspected and logged.

Deploy on MCP Gateway

Before you start

What Intercom needs first

A user who can create and configure an OAuth app in the Intercom Developer Hub does the Intercom side of the setup.

  • The workspace must be hosted in the US or EU. Australian-hosted workspaces are not supported.
  • You need permission to create and configure an OAuth app for the workspace.
  • Intercom does not name a required plan or administrator role.

In Intercom

  1. Identify the workspace region from its hostname.
  2. Create an app in the Developer Hub.
  3. Enable OAuth, add the Speakeasy redirect URL, and select read permissions.
  4. Copy the Client ID and Client secret.
Full Intercom setup guide in the docs

Set up

Add Intercom to Claude Code in 4 steps

  1. 01

    Add Intercom from the catalog

    An admin finds Intercom in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Intercom uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Intercom

    Give teams the mcp:connect scope on the Intercom server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Intercom to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Intercom from Claude Code

    The first time Claude Code connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Intercom needs its own OAuth grant, so each person connects it once. Until they do, Intercom calls fail while the rest of the gateway keeps working.

    From then on, Intercom's tools appear in Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Intercom

Reproduce a bug from a conversation

Paste the Intercom conversation URL into Claude Code. It reads the full message history, then the contact's custom attributes and signup details, so you can set up the same conditions locally.

get_conversationget_contact

Gauge how many customers hit an error

Before deciding how urgent a fix is, have Claude Code search conversations that mention the error and count how many are still open.

search_conversations

Check the help article before a change

When you change how a feature behaves, Claude Code finds the Help Center article that documents it and tells you which steps will be out of date.

search_articlesget_article

Tools

13 tools

Each Intercom tool can be allowed or denied per team and role at the MCP Gateway before Claude Code sees it.

search_conversations

Search for Intercom conversations using multiple filter criteria.

get_conversation

Retrieve complete details for a specific Intercom conversation.

search_contacts

Search for Intercom contacts using multiple filter criteria.

get_contact

Retrieve complete details for a specific Intercom contact.

list_companies

List Intercom companies with optional filters.

get_company

Retrieve complete details for a specific Intercom company.

See all 13 tools

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code exposes to Speakeasy.

Tool logs

Gateway

Every Intercom call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Intercom tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Intercom can reject a tool request before it reaches the server, or withhold a result from Claude Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Which Intercom workspaces can connect through Speakeasy?
Workspaces hosted in the US or EU. Intercom does not support its MCP server for Australian-hosted workspaces.
Can I see which developer read a customer conversation?
With Claude Code's OpenTelemetry exporter configured, each session is tied to a named person. Without it, activity can't be attributed.
How do Claude Code users get Intercom?
An admin adds Intercom from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Intercom tools their access allows.
Are Intercom calls from Claude Code logged?
Yes. Intercom calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Intercom in other clients

AI everywhere.

Control here.