MCP field guide / Intercom
// mcp field guide · support
You'd expect a support MCP to be all about the irreversible customer reply — but honestly, Intercom's isn't, yet. The official server exposes 13 tools that are overwhelmingly read; its only writes are Help Center article create/update. There's no reply-to-customer, no delete, no internal-note tool today. So the honest guard verdict is moderate, not strong.
GUARD FIT · READS (11 tools)
PASS-THROUGHUniversal search + lookups across conversations, contacts, companies, articles. No state change.
GUARD FIT · ARTICLE WRITES
MODERATEcreate_article/update_article publish/modify public, customer-visible Help Center content — reversible-with-effort.
Overall fit: MODERATE — because the sharp edges (customer reply, deletes) aren't in this MCP's tool surface today.
Intercom's official server is hosted (mcp.intercom.com/mcp, EU at mcp.eu.intercom.com/mcp), OAuth or Bearer, permission-scoped to the caller. It's a read/retrieval surface — universal search plus targeted lookups across conversations, contacts, companies, and Help Center articles — with the only write capability being article create/update.1 (Note: Intercom's GitHub README currently reads as an older 6-tool/read-only revision; the docs page is the more current 13-tool source — treat the docs as canonical.)
| Tier | Tools |
|---|---|
| read-only | search, fetch, search_conversations, get_conversation, search_contacts, get_contact, list_companies, get_company, list_articles, search_articles, get_article |
| mutating (customer-visible) | create_article, update_article — publish/edit public Help Center content |
| consequential | none exposed — no reply, tag, internal-note, assign, or delete-contact tool in the current 13-tool surface |
The honest non-finding: the risk you'd anticipate on a support tool — a customer-facing reply that emails the customer (irreversible once sent), or a contact delete — is not in this MCP server. Those actions exist in Intercom's REST API but aren't surfaced here as of Aug 2026. We mark them absent, not present. If Intercom later adds a reply/message tool, that becomes the strong gate (an irreversible customer send, like Zendesk).
Support triage / analytics. "Search open conversations mentioning X, summarize the last 20" — pure reads.
Contact/company context. Pull a contact's attributes + company record to ground an agent's answer.
Help Center ops. Draft, create, and update KB articles — the one write path.
Reads → pass through. Eleven of the thirteen tools; no blast radius.
Article writes → moderate. create_article/update_article publish or modify public, customer-visible content. An impact diff of the article body before commit is exactly the ChronoMCP pattern — and since an edit is revertible, the honest label is "reversible-with-effort," not "irreversible."
The honest pitch: on today's Intercom MCP, gate the two article writes; the high-stakes "irreversible customer send" gate is a story about Intercom's API or a future MCP surface, not the current tools. We'd rather tell you that than manufacture a danger that isn't there — which is the same discipline that makes the rest of this guide trustworthy.
ChronoMCP passes Intercom's reads through and holds create_article/update_article for a human — ready for the day a reply tool appears.
Profiles describe third-party software from its public sources; ChronoMCP is not affiliated with Intercom. Reply/tag/note/assign/delete tools are reported as absent from the current official surface, not guessed. Risk groupings are our classification. Sources current as of Aug 2026 (the toolset is expanding) — check the source links.