MCP Ecommerce
Find your MCP

Installation guide

How to install Intercom MCP Server

In Claude Desktop, ChatGPT, Cursor and Claude Code, with what to check before you start and the first prompts to run.

Intercom hosts this MCP server, so there is nothing to install on a server. You add the server URL for your region to your AI client and sign in with OAuth, which the documentation recommends. A bearer token is also supported. Your browser first shows an Intercom MCP consent page, then Intercom's own authorization screen. The server covers conversations, contacts, companies and Help Center articles. It has 14 tools, some read-only and some that write.

A support lead or Intercom admin should do this, using an account whose permissions they are comfortable giving the AI client. Start read-only. Write tools (add_internal_note, create_article, update_article) should only be used for supervised tasks. Adding a note needs the Write conversations permission, and it can unsnooze a snoozed conversation assigned to someone else.

Intercom MCP Server setup guide: Intercom's MCP documentation page on developers.intercom.com, shown in a browser frame (support and reviews MCP server for e-commerce)
Intercom MCP Server setup guide preview: Intercom’s documentation on developers.intercom.com, captured Oct 13, 2026. The page may have changed since; the link opens the live version.

Before you start

  • An Intercom workspace hosted in the US or EU. AU hosted workspaces are not supported yet.
  • Knowing your region: app.intercom.com means US, app.eu.intercom.com means EU.
  • An Intercom login whose permissions you are happy for the AI client to use. Write tools also need the Write conversations permission.
  • An AI client that supports remote MCP servers, such as Claude Desktop, Claude Code, Cursor, or ChatGPT with custom connectors if your plan offers them.
  • If you use a bearer token instead of OAuth, an Intercom API token stored somewhere private, not in a shared file.
How it runs
Remote, added by URL
Access
Varies by tool
Server address
https://mcp.intercom.com/mcp

Intercom MCP Server in Claude Desktop

  1. Check your workspace URL. app.intercom.com is US and uses https://mcp.intercom.com/mcp. app.eu.intercom.com is EU and uses https://mcp.eu.intercom.com/mcp.
  2. Open the MCP setup guide for Claude Desktop that the Intercom documentation links, and follow it for adding a server.
  3. Add the server using the Streamable HTTP URL for your region. The Intercom documentation also gives a generic template that runs npx with mcp-remote and the endpoint URL. Check the exact format against Anthropic's guide, because the template is generic.
  4. Restart Claude Desktop if the guide says to, then start the connection and sign in with OAuth.
  5. On the Intercom MCP consent page, check the application name and the Redirects to address. Choose Allow if they match what you expect, or Cancel if not. Then approve Intercom's authorization screen.
  6. Run one of the read-only prompts below before using any write tool.

Intercom MCP Server in ChatGPT

  1. The Intercom documentation links an OpenAI MCP integration guide but does not cover ChatGPT's menus, so follow OpenAI's current instructions for your plan.
  2. Check your workspace region and pick the matching Streamable HTTP URL: https://mcp.intercom.com/mcp for US or https://mcp.eu.intercom.com/mcp for EU.
  3. In ChatGPT, open the settings area for connectors or integrations and add a custom remote MCP server by URL. Your plan or workspace admin may need to allow this.
  4. Paste the endpoint URL and choose OAuth when asked for authentication.
  5. On the Intercom MCP consent page, check the application name and the Redirects to address. Choose Allow only if you recognize them, then approve Intercom's authorization screen.
  6. Start a chat with the connector enabled and run a read-only prompt first.

Intercom MCP Server in Cursor

  1. Check your workspace region. Use https://mcp.intercom.com/mcp for US or https://mcp.eu.intercom.com/mcp for EU.
  2. Open Cursor's MCP configuration guide, which the Intercom documentation links, and find where MCP servers are configured.
  3. Add a server named intercom. The documentation's generic template uses the command npx with the arguments mcp-remote and the endpoint URL. Confirm the format against Cursor's guide.
  4. Save the configuration and, if needed, reload Cursor so the server appears in its MCP list.
  5. Complete OAuth in the browser. Check the application name and Redirects to address on the consent page, choose Allow, then approve Intercom's authorization screen.
  6. Run a read-only prompt to confirm the tools are available.

Intercom MCP Server in Claude Code

  1. Check your workspace region. Use https://mcp.intercom.com/mcp for US or https://mcp.eu.intercom.com/mcp for EU.
  2. Open the Claude Code MCP setup documentation that the Intercom documentation links. The Intercom page does not give a Claude Code command, so take the exact command and flags from that guide.
  3. Add Intercom as a remote server using the Streamable HTTP URL for your region, not the deprecated Legacy SSE one.
  4. Start the OAuth sign-in when Claude Code prompts for it. On the Intercom MCP consent page, check the application name and Redirects to address, then choose Allow.
  5. Approve Intercom's authorization screen and return to Claude Code.
  6. Confirm the server is listed as connected, then run a read-only prompt.

Check that it works

Start with questions that only read data. If these answer from your real account, the connection is good.

  • Search open Intercom conversations and list the five most recent with their state and assignee.
  • Search Intercom contacts with the email domain example.com and show their names and emails.
  • Search the Help Center for articles about refunds and show the title and state of each result.

Troubleshooting

+Why do I get a 401 when I try to add an internal note?

The documentation says a 401 usually means your workspace's Intercom connection predates the Write conversations permission. Disconnect and reconnect the Intercom integration to grant it. Also check that the ID is a regular conversation, because ticket IDs are not supported and return an authorization error.

+Why can't I connect, or why does sign-in fail for my workspace?

First confirm your region. app.intercom.com is US and app.eu.intercom.com is EU, and each needs its own endpoint. AU hosted workspaces are not supported yet. In Claude.ai, the directory connector only reaches US workspaces, so EU workspaces need a custom connector with the EU endpoint.

+The consent page shows an application or redirect address I do not recognize. What now?

Choose Cancel, which grants nothing. The application name is supplied by the application itself and Intercom does not verify it, so the Redirects to address is the useful check. Only choose Allow if you started the connection and the address belongs to the client you are setting up.

Written Oct 13, 2026 from the vendor documentation. Exact menus, addresses and commands change; the official documentation is the source of truth.