Setting up the Intercom MCP Server

The Intercom MCP Server exposes conversations, contacts, companies, and help center articles from an Intercom account to external AI clients. This guide covers setup and the difference between the two regional endpoints.

Determine your region

Before setup, check in your own Intercom account whether the workspace is hosted in the US or the EU. US workspaces use the endpoint https://mcp.intercom.com/mcp, EU workspaces use https://mcp.eu.intercom.com/mcp. AU-hosted workspaces are not currently supported by the server.

Establish the connection

In MCP clients with native remote support, the server URL for the matching region is enough. For clients without native support, mcp-remote can be used as a helper tool:

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

Choose authentication

For most use cases, Intercom recommends OAuth: on first connection, a consent screen opens in the browser where the desired permissions are granted. Anyone who prefers a fixed bearer token instead, for example for non-interactive automation, can set it directly in the client configuration.

Choose permissions deliberately

When granting OAuth consent or creating a token, select only the scopes actually needed — for example "Read conversations" for pure read use cases, instead of also enabling "Write conversations" or "Read and write articles" when no write actions are planned.

Test the first request

After setup, try a harmless read operation first, for example listing help center articles or searching for a known contact. This verifies the connection before write tools like create_article, update_article, or add_internal_note are used in production.

Watch rate limits

Per the provider, the regular Intercom API limits apply to the MCP server. If you see frequent rate-limit errors, reducing request frequency or batching requests helps.

Source: developers.intercom.com/docs/guides/mcp, checked on 2026-09-23.