Intercom MCP Server
Connect AI agents to Intercom conversations, contacts, and customer data via the official MCP server.
Updated
What is Intercom MCP?
The Intercom MCP server is a Model Context Protocol server that lets AI agents and assistants securely access your Intercom customer-support data — conversations, contacts, and related metadata — through a standardized interface.
It is an officially hosted, remote MCP server operated by Intercom at https://mcp.intercom.com/mcp (Streamable HTTP; a legacy /sse endpoint also exists but is deprecated). Because Intercom hosts it, there is nothing to deploy or self-host — clients connect directly to the URL and authenticate over OAuth, so the agent only ever sees data your authorized scopes permit.
The server exposes read-oriented tools for universal and targeted search across conversations and contacts, plus detailed fetch of individual records. This brings live customer context into AI tools like Claude and Cursor, so support, sales, and product teams can pull insights from real conversations and user profiles without leaving their assistant. Note: the server is currently supported only in US-hosted Intercom workspaces.
Tools the Intercom MCP server exposes
| Tool | What it does |
|---|---|
| search | Universal search tool for finding conversations and contacts using a query DSL approach. |
| fetch | Retrieve complete detailed information for a specific resource. |
| search_conversations | Search conversations with advanced filtering by source type, author, state, assignment, and timing. |
| get_conversation | Retrieve a single conversation by ID with all conversation parts and metadata. |
| search_contacts | Search contacts by ID, name, email, phone, custom attributes, or email domain. |
| get_contact | Get complete contact information including custom attributes, location, and activity timestamps. |
Connect the Intercom MCP server
Claude Code
- 1
Add the remote server
Run: claude mcp add --transport http intercom https://mcp.intercom.com/mcp
- 2
Authenticate with OAuth
On first use, Claude Code opens a browser to complete Intercom's OAuth flow; approve the requested read scopes for your US-hosted workspace.
- 3
Verify the connection
Run /mcp inside Claude Code to confirm Intercom is connected and its tools (search, fetch, search_conversations, etc.) are listed.
Cursor
- 1
Open MCP settings
In Cursor, go to Settings -> MCP -> Add new MCP server.
- 2
Add the Intercom server
Add an entry pointing to https://mcp.intercom.com/mcp. If your config requires a command, use: npx mcp-remote https://mcp.intercom.com/mcp
- 3
Complete OAuth and confirm
A browser window opens for Intercom OAuth; approve access. Cursor then lists the Intercom tools as available in chat.
Sample use cases
Support triage
An agent fetches the relevant conversation and contact details on a new ticket to summarize and route it.
Customer context for sales
Pull a contact's recent conversations and attributes into an AI assistant before an outreach or call.
Insight mining
Search across conversations to surface recurring themes and customer pain points.
Security & permissions
Authentication uses OAuth (browser-based, recommended) or a direct Bearer token. Under OAuth, the agent acts with the scopes you approve — Intercom requires scopes such as "Read and list users and companies" and "Read conversations." The exposed tools are read/search-oriented over conversations and contacts, so the agent gets visibility into customer-support data but does not gain broad write access through these tools. Access is currently limited to US-hosted Intercom workspaces. Review and minimize granted scopes, and revoke the OAuth grant from Intercom if access is no longer needed.
Using Intercom MCP with Gamut
In Gamut, you connect Intercom once and an agent can then use the MCP server's search and fetch tools as part of an automated, event- or schedule-triggered workflow — for example, on a new-ticket webhook or a nightly run, the agent pulls the relevant conversation and contact context to triage, summarize, or route support issues. Gamut manages the OAuth connection and credentials, so the agent invokes Intercom's read tools securely within the scopes you approved, without manual token handling.
Frequently asked questions
What is the Intercom MCP server?
It is Intercom's official, hosted Model Context Protocol server at https://mcp.intercom.com/mcp. It gives AI agents a standardized, OAuth-secured way to search and read Intercom conversations and contacts so customer context can be used inside AI tools.
Is the Intercom MCP server free?
Intercom does not publish a separate price for the MCP server; access is tied to your existing Intercom workspace and the OAuth scopes you approve. It is currently available only to US-hosted Intercom workspaces.
How do I connect the Intercom MCP server to Claude or Cursor?
Point the client at https://mcp.intercom.com/mcp. In Claude Code, run 'claude mcp add --transport http intercom https://mcp.intercom.com/mcp'; in Cursor, add the same URL (or 'npx mcp-remote https://mcp.intercom.com/mcp') under MCP settings. Both complete an OAuth flow in the browser on first use.
Is the Intercom MCP server hosted or self-hosted?
It is hosted and operated by Intercom as a remote MCP server — there is nothing to deploy. You connect directly to https://mcp.intercom.com/mcp and authenticate over OAuth.