Intercom MCP

Intercom MCP is the Model Context Protocol server that Intercom hosts for its own customers. It is a remote server at https://mcp.intercom.com/mcp (US) or https://mcp.eu.intercom.com/mcp (EU), documented on Intercom's developer hub, and it lets Claude, ChatGPT, Cursor, VS Code and other MCP clients search and read your conversations, contacts and companies, work with Help Center articles, and add internal notes to conversations. There is nothing to install from npm: Intercom does not publish an @intercom/mcp-server package.

Which Intercom MCP this page covers. Intercom runs a second, separate MCP server, the Fin Agent API MCP server at https://api.intercom.io/fin/mcp. That one lets an outside agent call Fin, Intercom's AI agent, to answer questions and run Fin procedures, and it authenticates with a Fin Agent API key. This page covers the workspace data server on mcp.intercom.com.

Quick facts (as of October 8, 2026)

Tools

Our count from the developer docs page is 14 tools, which matches the "14 tools" the page itself states.

Search tools return up to 150 results per page (5 by default) and use a starting_after cursor. list_companies and list_articles use page numbers instead.

Setup

Pick the URL for your workspace's region first. Intercom's docs say app.intercom.com means a US hosted workspace and app.eu.intercom.com means EU hosted.

Claude Code

Claude Code's documented pattern for a remote server is claude mcp add --transport http <name> <url>:

claude mcp add --transport http intercom https://mcp.intercom.com/mcp

Use https://mcp.eu.intercom.com/mcp for an EU workspace. Then run /mcp inside Claude Code and choose the server to complete the OAuth sign-in in your browser.

Claude.ai

Intercom's docs say the Intercom connector in Claude's directory connects to US hosted workspaces. For an EU workspace, go to Customize, Connectors, Add, Add custom connector, and enter https://mcp.eu.intercom.com/mcp. On Claude Team or Enterprise, an organization Owner adds it under Organization settings, Connectors.

Clients that use a JSON config (Claude Desktop and others)

Intercom's generic template runs the mcp-remote bridge with npx:

{
  "mcpServers": {
    "intercom": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.intercom.com/mcp"]
    }
  }
}

For token authentication, Intercom's template adds "--header", "Authorization:${AUTH_HEADER}" to args and sets AUTH_HEADER to Bearer YOUR_INTERCOM_API_TOKEN in an env block. Intercom says these are templates and points you to each client's own MCP docs (Claude Desktop, Claude Code, OpenAI, Cursor, Windsurf and VS Code) for exact steps.

To check the connection, Intercom suggests npx @modelcontextprotocol/inspector with the Streamable HTTP transport and your region's URL.

Authentication and permissions

OAuth is the recommended route. Your browser shows two screens: an Intercom MCP consent page that names the application asking for access, lists what it can do and shows the address it redirects to, and then Intercom's own authorization screen. Intercom notes that the application name on the consent page is supplied by the application and not verified, so check the redirect address before you choose Allow. The consent page expires after 15 minutes.

The server needs these Intercom permissions:

• Read and list users and companies
• Read conversations
• Write conversations, for add_internal_note
• Read and write articles, for the five article tools

With Bearer token authentication, your token must include those scopes. Notes are attributed to the admin who authorized the connection, and cannot be set per call.

If you build your own MCP client, the server supports Dynamic Client Registration, but every OAuth redirect URI is checked against an allowlist. Localhost callbacks are allowed on any port; anything else needs an entry from Intercom Customer Support.

Limitations and things to watch

• It is not read-only. An agent can create and update public Help Center articles and add notes to conversations. Keep tool approval on in your client, especially for update_article.
• A note can reopen a conversation. Intercom's docs say a note on a snoozed conversation assigned to someone other than the authorizing admin will unsnooze it.
• No customer-facing replies. add_internal_note cannot send anything to the customer, and no tool listed sends messages.
• Tickets are not supported by the note tool. Ticket IDs return an authorization error.
• Wrong region fails late. Using the US URL with an EU workspace leads to a "We're having technical difficulties" error after you choose Allow.
• AU workspaces cannot use it yet.
• Older connections may lack the write scope. Intercom says a 401 on add_internal_note usually means you should disconnect and reconnect to grant Write conversations.
• Intercom API rate limits apply.
• Official pages disagree. Intercom's integrations page and the GitHub README still say US only, and the README lists 6 tools. The developer docs, read on October 8, 2026, are the most current source.

Pros and cons

Pros

• Official and hosted by Intercom, with nothing to install for clients that support remote servers.
• OAuth sign-in with a consent page that shows which app gets access.
• Covers conversations, contacts, companies and Help Center articles in one server.
• EU endpoint processes requests within the EU.
• Write access is narrow: articles and internal notes only.

Cons

• No source code published, so you cannot audit or self-host it.
• Write tools mean it is not a safe "read only" connection by default.
• No AU region.
• No tools for tickets, tags, admins or sending replies in the documented list.
• Some official pages are out of date.

Who it is for

A good fit if:

• Your support team runs on Intercom and you want an assistant to search conversations, summarize a customer's history or look for recurring themes.
• You maintain a Help Center and want an agent to draft or update articles for review.
• You want to leave internal notes on conversations from your AI client.

Not the right tool if:

• You want an outside agent to answer customers using Fin. That is the Fin Agent API MCP server.
• Your workspace is AU hosted.
• Your helpdesk is Zendesk. See the Zendesk MCP server instead, or the HubSpot MCP server if your support data lives in HubSpot.

What we could not verify

• Plan requirements. The developer docs do not say which Intercom plans can use the MCP server.
• Rate limits specific to the MCP server. The docs only say Intercom API limits apply.
• Whether the Claude.ai directory connector exposes all 14 tools.
• A license. There is no published source code and no license file.
• How the server behaves in practice. We did not run it.

How this page was put together

We read Intercom's MCP developer guide, the Intercom MCP Server integration page, the Fin Agent API MCP Server help article, the Intercom pricing page, the intercom/intercom-mcp-server GitHub repository, the npm registry and Claude Code's MCP docs on October 8, 2026. We did not run the server.

Sources

• Intercom Developers: Model Context Protocol (MCP)
• Intercom: Intercom MCP Server integration
• Intercom Help: Fin Agent API, MCP Server
• Intercom pricing
• GitHub: intercom/intercom-mcp-server
• Claude Code docs: Connect Claude Code to tools via MCP
• npm registry lookup for @intercom/mcp-server (returns Not found, checked October 8, 2026)