MCP Gateway · Claude Cowork
Connect Intercom to Claude Cowork
Support leads want a regular report on why customers write in and where the Help Center falls short. Cowork can produce it in one long session, reading many Intercom conversations and articles, once the plugin carrying Intercom is synced from Speakeasy's marketplace. Agent hooks pass each prompt to Speakeasy for a decision first.
- Category
- Communication
- Tools
- 13
- Authentication
- OAuth
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork connects to the Intercom server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Intercom from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Intercom
Write the weekly support trends report
Cowork searches the week's closed conversations, reads a sample of each common topic, and writes a report on the top themes with example quotes.
Find gaps in the Help Center
Cowork compares the questions customers ask most with the published articles, and lists the topics that have no article or an outdated one.
Profile accounts with repeat contacts
For companies that contact support most often, Cowork pulls each company's plan, size and custom attributes, and looks for patterns across them.
Tools
13 tools
Each Intercom tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Does Cowork need the device agent to use Intercom?
Which Intercom plan does the workspace need?
How do Claude Cowork users get Intercom?
Are Intercom calls from Claude Cowork logged?
Connect more