MCP Gateway · Claude
Connect Intercom to Claude
Long support threads take time to read before anyone can reply. When Intercom is added as a custom Claude connector pointing at the Speakeasy gateway, support agents ask Claude to read a conversation and the customer's account, then help write the answer. People see only what their role permits.
- Category
- Communication
- Tools
- 13
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
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.
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
- Identify the workspace region from its hostname.
- Create an app in the Developer Hub.
- Enable OAuth, add the Speakeasy redirect URL, and select read permissions.
- Copy the Client ID and Client secret.
Set up
Add Intercom to Claude in 4 steps
- 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.
- 02
Choose who can use Intercom
Give teams the
mcp:connectscope 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. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Intercom from Claude
The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Intercom
Summarize a long thread
Paste a conversation link and Claude reads the complete message history, then lists what the customer asked, what was tried and what is still unresolved.
Draft a reply from the Help Center
Claude searches published Help Center articles for the customer's question and drafts a reply that links the article that answers it.
Check the account before escalating
Before you escalate, ask Claude for the customer's company profile, including plan, monthly spend and user count, so the escalation has the context.
Tools
13 tools
Each Intercom tool can be allowed or denied per team and role at the MCP Gateway before Claude 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.
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can Claude conversations that read Intercom data be audited?
Does adding Intercom to Claude need an OAuth client for each person?
How do Claude users get Intercom?
Are Intercom calls from Claude logged?
Connect more