--- title: "Intercom MCP Server: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/mcp-servers/intercom/ description: "Hosted Intercom endpoint for searching conversations and contacts and fetching full records, with read-scoped OAuth or bearer credentials." --- # Intercom MCP Server: review, setup & limitations · Undominated.ai > Hosted Intercom endpoint for searching conversations and contacts and fetching full records, with read-scoped OAuth or bearer credentials. [← Explore all mcp servers](/mcp-servers/) CUSTOMER SUPPORT / Intercom # Intercom MCP Server Hosted Intercom endpoint for searching conversations and contacts and fetching full records, with read-scoped OAuth or bearer credentials. [See setup guidance ↓](#setup)[Original source ↗](https://github.com/intercom/intercom-mcp-server) SOURCE REVIEW Reviewed 2026-10-07 Evidence 1 linked sources Publisher Intercom Licence Not established Revision 96140be28cf8 [Read what was—and wasn’t—checked ↓](#review) “Hosted Intercom server for searching conversations and contacts.” [Intercom · upstream description ↗](https://github.com/intercom/intercom-mcp-server/blob/96140be28cf8eeb2ae4a4c860ca1eddcdfb006d9/README.md) Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Publisher-documented support-triage surface: conversation and contact search plus full-record fetch in six tools. - Required token scopes are read scopes, so the documented surface is observational rather than mutating. ### A good fit for - Finding open conversations about a refund or outage during support triage. - Pulling a contact's full record and conversation history before replying. ### Weigh up before choosing - Only US hosted workspaces are supported at the reviewed revision. - The legacy SSE URL is deprecated; Streamable HTTP is the documented path. - Bearer tokens need the documented read scopes; broader tokens widen what any misconfigured client can reach. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - README.md: connection URLs, six documented tools, OAuth versus bearer setup and required read scopes. - Repository manifest check: no runtime package manifest at the pinned revision; the repository is documentation for the hosted server. ### Our findings - Documented tools are search and fetch operations over conversations and contacts; no reply, assign or mutation tool is listed. - Both OAuth and bearer paths target the same hosted endpoint; scopes, not transport, bound the access. ### Not established by this review - Server connection, authentication and tool execution were not tested. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Connect a server deliberately. [Upstream setup instructions ↗](https://github.com/intercom/intercom-mcp-server) - Add the documented mcp-remote configuration pointing at the hosted Streamable HTTP URL. - Complete OAuth, or attach a bearer token carrying only the documented read scopes. ### Before you start - An Intercom account on a US hosted workspace with permission to grant the read scopes. ### Documented configuration example Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts. { "mcpServers": { "intercom": { "command": "npx", "args": [ "mcp-remote", "https://mcp.intercom.com/mcp" ] } } } Copy configuration ↗ ### Compatibility MCP clients supporting Streamable HTTP, directly or via the documented mcp-remote bridge. · An Intercom account with OAuth consent or a bearer token carrying the read scopes. ### Transports Streamable HTTP · SSE ### Intercom OAuth or bearer token - Reads conversations and contacts visible under the granted read scopes. - No mutation tool is documented; the surface is observational within its scopes. ### Cost model Intercom plan and seat entitlements apply; the documentation carries no separate licence. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - [Intercom MCP server readme ↗](https://github.com/intercom/intercom-mcp-server/blob/96140be28cf8eeb2ae4a4c860ca1eddcdfb006d9/README.md) Checked 2026-10-07 https://github.com/intercom/intercom-mcp-server/blob/96140be28cf8eeb2ae4a4c860ca1eddcdfb006d9/README.md Supports: summary, install, compatibility, access, transports, configExample, whySelected, bestFor, limitations KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Resend MCP ↗ Connects an assistant to Resend email sending, delivery records and account operations through hosted or local MCP.](/mcp-servers/resend/)[### Asana MCP V2 ↗ Asana’s current workspace-scoped MCP connection for task, project and portfolio workflows.](/mcp-servers/asana/)[### Auth0 MCP Server ↗ Configures a local Auth0 MCP connection with an explicit read-only tenant-tool selection.](/mcp-servers/auth0-auth0-mcp-server/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/) ## Continue your investigation - [Inspect resource evidence](/tools/) - [Choose a host](/agents/) - [Inspect reusable workflows](/skills/) - [Use Undominated data](/api/)