This profile is part of our MCP server directory, within The MCP Guide. Profiles are checked against each vendor's own documentation. Need a server built? See MCP development.
Intercom's MCP server lets an AI app search and read conversations, contacts, companies and Help Center articles, add internal notes, and draft articles. Intercom hosts it with separate US and EU endpoints and documents setup for Claude, Cursor, VS Code and others.
Checked against: Intercom's MCP server guide on 28 October 2026. eSEOspace did not install or test this server.
Key Takeaways
- Intercom runs the server at
https://mcp.intercom.com/mcp(US) andhttps://mcp.eu.intercom.com/mcp(EU); AU-hosted workspaces are not supported. - It has 14 core tools, mostly read-only, plus 5 Fin Operator tools for workspaces that have Fin Operator.
- The write tools are
create_article,update_articleandadd_internal_note, plusapply_proposalsandreject_proposalsfor Fin Operator. - OAuth is recommended; a bearer token also works but cannot use Fin Operator tools.
- Intercom warns that the app name on the consent page is supplied by the app and is not verified.
At a glance
| Item | Detail |
|---|---|
| Publisher | Intercom |
| Official? | Yes |
| Hosting | Remote URLs (US and EU) |
| Transport | Streamable HTTP (recommended); legacy SSE deprecated |
| Sign-in | OAuth (recommended) or bearer token |
| Read or write | Mostly read; a few write tools |
| Price | No separate MCP price listed; Fin Operator tools need Fin Operator |
| Source code | Closed |
| Status | Not stated; SSE transport is deprecated |
What it can do
Intercom's MCP guide lists each tool and whether it reads or writes.
| Tool | Access | Purpose |
|---|---|---|
search | Read | Search conversations and contacts with a query syntax |
fetch | Read | Full details for IDs returned by search |
search_conversations, get_conversation | Read | Find and open conversations |
search_contacts, get_contact | Read | Find and open contacts |
list_companies, get_company | Read | List and open companies |
list_articles, search_articles, get_article | Read | Help Center articles |
create_article | Write | Create an article (draft by default) |
update_article | Write | Update an article |
add_internal_note | Write | Add a teammate-only note to a conversation |
Fin Operator tools appear only when the workspace has Fin Operator and the connection uses OAuth: send_operator_message, get_operator_response, get_proposal_details, apply_proposals and reject_proposals. Intercom says send_operator_message is the only tool that uses Operator credits, and apply_proposals changes your live workspace configuration.
How to connect it
Pick the endpoint for your workspace region. app.intercom.com is US-hosted and app.eu.intercom.com is EU-hosted. Intercom says EU requests are processed within the EU.
| Region | Streamable HTTP |
|---|---|
| US | https://mcp.intercom.com/mcp |
| EU | https://mcp.eu.intercom.com/mcp |
Intercom lists Claude Desktop, Claude Code, Claude.ai, OpenAI, Cursor, Windsurf (now Devin Desktop) and VS Code as supported clients. Custom clients can connect through Dynamic Client Registration. Intercom says most clients connect by running npx mcp-remote with the server URL, and for bearer tokens the token goes in an Authorization header. It recommends checking your client's own docs for exact steps.
To test, Intercom suggests the MCP Inspector:
npx @modelcontextprotocol/inspectorChoose Streamable HTTP and enter your region's URL. If you see "We're having technical difficulties" after selecting Allow, Intercom says you probably used the wrong region's endpoint.
Security notes
- Check the consent page. Intercom says the application name on its consent page "is supplied by the application and is not verified." Check the redirect address before you select Allow, and select Cancel if you did not start the connection.
- Permissions. OAuth asks for read users and companies, read conversations, write conversations (for
add_internal_note), read and write articles, and use Fin Operator. - Internal notes have side effects. Notes are attributed to the admin who authorized the connection, and they can reopen a snoozed conversation assigned to someone else.
- Live config changes.
apply_proposalsapplies Fin Operator proposals to your live workspace. Reviewget_proposal_detailsfirst. - Redirect allowlist. Custom client redirect URIs must be on an allowlist;
localhostcallbacks are allowed on any port. - Rate limits. Intercom API rate limits apply.
Customer messages are untrusted text that the AI will read. Read MCP prompt injection, MCP confused deputy and the MCP Security Center.
Alternatives
- Front MCP server: shared inbox tools, including drafts and a separate send scope.
- Freshdesk MCP server: Freshworks' help desk server with ticket and knowledge base tools.
- HubSpot MCP server: CRM plus conversation search across chat, email and WhatsApp.
Next step
A good first use is read-only triage: summarize open conversations and find matching Help Center articles. Add write tools later. For more support-desk options, browse the MCP server directory, or ask us about MCP development for a custom workflow.
Frequently asked questions
Does the Intercom MCP server work for EU workspaces?
Yes. Intercom provides https://mcp.eu.intercom.com/mcp for EU-hosted workspaces and says EU requests are processed within the EU. AU-hosted workspaces are not supported.
Can the AI reply to customers through Intercom MCP?
Not according to the tool list we checked. The conversation write tool is add_internal_note, which adds a note only teammates can see.
What is the difference between OAuth and a bearer token?
Intercom recommends OAuth, which uses a browser consent step. A bearer token is a direct API token, and Intercom says it cannot receive the Fin Operator permission or tools.
Why does add_internal_note return a 401 error?
Intercom says the tool needs the Write conversations permission. A 401 usually means you need to disconnect and reconnect the integration so it gets that permission.
