Ranked roundup · Intercom
Best MCP Server for Intercom
There is an official MCP server for Intercom, and it is the right starting point for most teams. Intercom hosts it at mcp.intercom.com/mcp, ships 13 tools, and authenticates over browser OAuth — nothing to install, nothing to host. The catch: it is almost entirely read-only. The only write path is Help Center articles, and it serves US and EU hosted workspaces only (AU is not supported yet). That gap is why managed platforms matter here. Composio exposes 133 Intercom actions behind managed OAuth, including replying to and assigning conversations; Zapier MCP offers a smaller, explicitly scoped set of write actions. The open-source side is genuinely thin: the best-known community servers sit at around 8 GitHub stars each, and neither has been pushed to since April 2025. We list them with those numbers rather than pretend otherwise. Rankings come from verifiable criteria — official status, maintenance recency, auth model, and documented capability coverage — not paid placement.
Facts checked September 1, 2026 · ranked on verifiable criteria · placement is never for sale
Founder, Automation Squad ·
The ranking
- Official · Intercom
Reading and analyzing conversations, contacts, and companies from Claude or any MCP client, plus drafting Help Center articles — with vendor support and no infrastructure.
13 tools: universal search and fetch, plus search_conversations, get_conversation, search_contacts, get_contact, list_companies, get_company, and Help Center article tools (list, search, get, create, update). Strong on reading conversations, contacts, and companies; article create/update is the sole write path.
Remote, hosted by Intercom (streamable HTTP at https://mcp.intercom.com/mcp; EU workspaces use https://mcp.eu.intercom.com/mcp). Nothing to install. · OAuth (browser flow, recommended) or a bearer Intercom API token. Access is governed by the scopes you grant. · 7★
- Almost entirely read-only: it cannot reply to, assign, or close conversations — the only write tools are Help Center article create/update.
- US and EU hosted workspaces only; AU workspaces are not supported yet.
- Standard Intercom API rate limits apply to all requests.
- The GitHub repo (intercom/intercom-mcp-server) is documentation only, 7 stars, no license file — the server itself is closed-source and hosted.
- Community
Agents that need to act on Intercom — triage, reply, assign, tag — not just read from it.
133 documented Intercom tools, including the writes the official server lacks: reply to, assign, close, and reopen conversations; create and update tickets; tag contacts, conversations, and tickets; manage companies, articles, events, and exports.
Fully hosted and managed by Composio; connect from Claude, Cursor, ChatGPT, or any MCP client via their endpoint. · Managed OAuth2 with automatic token refresh; you can swap in your own Intercom OAuth credentials for production.
- Not vendor-official: Composio sits between your assistant and your Intercom data (it claims SOC 2 Type 2 and ISO 27001 compliance, which we did not independently audit).
- Free to start, but it is a commercial platform — sustained usage moves onto paid plans.
- A 133-tool surface with write access deserves scoping: grant only the actions your agent actually needs.
- Community
Teams already on Zapier who want a small, explicitly scoped set of Intercom write actions with the least possible setup.
A curated set of write actions you enable individually: add a note or tag to a contact, create a Help Center article, create a conversation, create or update companies and users, update tickets, submit data events, remove tags.
Hosted by Zapier; you generate a personal MCP endpoint and point any MCP client at it. No code. · Intercom connects through Zapier's existing OAuth integration; the MCP endpoint itself is tied to your Zapier account.
- Geared toward write actions rather than deep conversation search — it is a poor fit for analytics-style querying.
- Usage counts against your Zapier plan's limits.
- Another third party in the path between your AI tool and customer data.
- Community
Teams that need conversation search on their own infrastructure and will accept maintaining an unofficial dependency.
Read-focused: list and search conversations and tickets with server-side filtering by date range, customer, status, and keywords, including searching by email content when no contact exists.
Self-hosted: Node.js 18+ via npm (mcp-server-for-intercom) or Docker. · Intercom access token supplied as a plain environment variable (INTERCOM_ACCESS_TOKEN) — no OAuth. · Apache-2.0 · 8★
- Unofficial and lightly adopted: 8 GitHub stars as of September 2026.
- Last pushed April 2025 — roughly 16 months without a commit at verification time.
- Read-only; no conversation reply, assignment, or ticket writes.
- A long-lived API token in an env var is a weaker security posture than the official server's OAuth scopes.
- Community
A minimal local server for one-off conversation analysis, if you are comfortable running abandoned-looking code.
Read-only conversation querying with filters for date range, customer ID, and conversation state, returning conversation details, contact info, and response/reopen statistics.
Self-hosted: clone the repo, npm install, run locally over stdio. · Intercom API key in a local .env file (INTERCOM_API_KEY) — no OAuth. · 8★
- No license file, which makes reuse and modification legally ambiguous.
- Last pushed December 2024 — over 20 months without a commit at verification time.
- 8 GitHub stars; effectively a single-maintainer side project.
- Read-only, and requires cloning and building manually — no npm package.
Intercom MCP servers compared
| Server | Maintained by | Runs | Auth | License |
|---|---|---|---|---|
| Intercom official MCP server | Intercom | Remote, hosted by Intercom (streamable HTTP at https://mcp.intercom.com/mcp; EU workspaces use https://mcp.eu.intercom.com/mcp). Nothing to install. | OAuth (browser flow, recommended) or a bearer Intercom API token. Access is governed by the scopes you grant. | — |
| Composio Intercom MCP | Community | Fully hosted and managed by Composio; connect from Claude, Cursor, ChatGPT, or any MCP client via their endpoint. | Managed OAuth2 with automatic token refresh; you can swap in your own Intercom OAuth credentials for production. | — |
| Zapier MCP for Intercom | Community | Hosted by Zapier; you generate a personal MCP endpoint and point any MCP client at it. No code. | Intercom connects through Zapier's existing OAuth integration; the MCP endpoint itself is tied to your Zapier account. | — |
| mcp-server-for-intercom (raoulbia-ai) | Community | Self-hosted: Node.js 18+ via npm (mcp-server-for-intercom) or Docker. | Intercom access token supplied as a plain environment variable (INTERCOM_ACCESS_TOKEN) — no OAuth. | Apache-2.0 |
| mcp-intercom (fabian1710) | Community | Self-hosted: clone the repo, npm install, run locally over stdio. | Intercom API key in a local .env file (INTERCOM_API_KEY) — no OAuth. | — |
How to choose
Pick the official Intercom server if your work is reading — searching conversations, pulling contacts and companies, drafting Help Center articles — and your workspace is US or EU hosted. Pick Composio if your agent needs to act on Intercom: reply, assign, close, tag, manage tickets. Pick Zapier MCP if you want a small, hand-picked set of write actions and already run Zapier. Pick a self-hosted community server only if data must stay on your own infrastructure and you accept maintaining code that has not been touched in over a year.
How this ranking works
Every server here is real and was checked against its repository or vendor documentation on the date above — stars and licenses come from the GitHub API, not from memory. Order reflects verifiable criteria only: official support, maintenance recency, adoption, auth model, and documented capability coverage. We do not run paid placements, and we list every caveat we find, including the unflattering ones.
Common questions
- Does Intercom have an official MCP server?
- Yes. Intercom hosts one at https://mcp.intercom.com/mcp (EU workspaces: https://mcp.eu.intercom.com/mcp) with 13 tools covering conversations, contacts, companies, and Help Center articles. It works with Claude, ChatGPT, and any MCP-compatible client.
- How does authentication actually work?
- The official server initiates a browser OAuth flow when your client connects, so there is no API key to manage; a bearer Intercom API token also works. The self-hosted community servers skip OAuth entirely and take a long-lived access token in an environment variable, which is simpler but weaker security.
- Can the official server reply to or close conversations?
- No. Conversations, contacts, and companies are read-only through the official server — its only write tools create and update Help Center articles. For conversation replies, assignment, or ticket writes, you need a managed platform like Composio or Zapier MCP.
- Are the open-source Intercom MCP servers still maintained?
- Not actively, as of our September 2026 check. The two best-known repos each have 8 GitHub stars, with last pushes in April 2025 (raoulbia-ai, Apache-2.0) and December 2024 (fabian1710, no license). Treat them as reference code rather than supported software.
MCP servers we build
Automation Squad publishes its own open-source MCP servers and agent skills, documented with the same rules this ranking uses.