Intercom is included for three distinct agent surfaces: a hosted MCP over Helpdesk and Help Center data, a beta Fin Agent API MCP that lets external agents call Fin, and Fin acting as a governed client of selected external MCP tools.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Conversations, contacts, companies, and Help Center articles through the 13-tool Intercom server; Fin capabilities, answers, conversations, and audience-matched procedures through the five-tool Fin server; and administrator-selected third-party MCP tools used by Fin.
Search and fetch conversations or contacts, retrieve companies, and list/search/get Help Center articles; discover Fin capabilities and obtain Fin responses; or let Fin read from explicitly imported external tools.
The Intercom data MCP can create and update Help Center articles but does not document conversation/contact/company mutations. The beta Fin MCP can continue conversations and run procedures; Fin client connectors can invoke external actions only when those tools are imported and configured.
The data MCP recommends OAuth and also accepts bearer tokens with conversation, contact/company, and read/write article scopes. Fin MCP teammate access uses a workspace Fin Agent API key; end-user access uses a Messenger JWT bound to one verified user. Imported external tools use their configured OAuth or token access.
Limit the data MCP token to required scopes; discover Fin procedures per user before invocation; configure each external tool with audience rules and direct-use behavior; and review data mapping because external tool results can be exposed to the customer.
The Intercom data MCP supports US-hosted workspaces only, uses Intercom API rate limits, and retains legacy SSE only for compatibility. Fin Agent API MCP is beta and requires feature enablement. Fin can process one external connector call per turn.
First-party MCP tool catalog
The complete 13-tool list published for Intercom's remote tenant-data MCP server. It covers conversations, contacts, companies, and Help Center articles and is separate from Fin's ability to consume external MCP servers. Reviewed Jul 10, 2026. Available only for US-hosted workspaces. OAuth is recommended; bearer tokens are also supported. Required access includes users and companies read/list, conversation read, and article read/write scopes. Intercom API rate limits apply.
searchreadfetchreadsearch_conversationsreadget_conversationreadsearch_contactsreadget_contactreadlist_companiesreadget_companyreadlist_articlesreadsearch_articlesreadget_articlereadcreate_articlewriteupdate_articlewriteTry a broader name, group, action, or availability term.
Agent access
Support: Official MCP server + 3rd Party MCP services
Read scope: The 13-tool data server reads conversations, contacts, companies, and Help Center articles; the five-tool Fin server discovers user-matched capabilities and returns generated support responses; Fin connectors read only through tools made live by administrators.
Write scope: 2 of 13 reviewed named tools have a write, draft, or mixed action label, including create_article, update_article. Read each catalog boundary before enabling them.
Authentication: Data MCP: OAuth recommended or bearer token. Fin MCP: workspace API key for the trusted teammate endpoint or server-generated Messenger JWT for the per-user endpoint. Fin client connectors: third-party OAuth 2.0 or stored token where supported.
Approval boundary: Intercom documents tool configuration and audience controls but not universal runtime confirmation. BYO-UI should confirm article publication or structural edits, Fin procedure execution, and any externally visible or state-changing connector call; informational reads can follow the active identity and scope.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Intercom ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
data MCP objects and tools, article writes, authentication, scopes, region, pagination, transport, and limits
Thirteen tools, article mutations, scopes, US availability, transport, pagination, and limits reviewed 2026-07-22
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party webhook, event, SDK, embedded-app, or extension documentation.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Fin MCP tools, beta maturity, identity, and permissions
Fin MCP tools, beta maturity, identity, and permissions reviewed from live first-party material on 2026-07-22.
Fin MCP client governance and limits
Fin MCP client governance and limits reviewed from live first-party material on 2026-07-22.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.