BYO-UI
Intercom

Intercom

Curated anchor platform in customer service, messaging, and support with material relevance to the Marcom operating stack and a first-party developer surface.

CRM, revenue & customerSystem of recordBYO-UI-ready platform
Representative source ↗Product site ↗
System roleSystem of record
Access maturityBYO-UI-ready platform
Agent postureFirst-party provider
Reference updatedNot stated by publisher
BYO-UI reviewedJul 10, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

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.

01 · Records and state owned

Search and retrieve conversations, contacts, companies and Help Center articles; create and update Help Center articles. Separate Fin MCP exposes Fin as a callable support agent

02 · Data you can retrieve

Search and retrieve conversations, contacts, companies and Help Center articles; create and update Help Center articles. Separate Fin MCP exposes Fin as a callable support agent

03 · Actions and write paths

Intercom's first-party MCP/agent surface includes state-changing tools in the documented capability area: Search and retrieve conversations, contacts, companies and Help Center articles; create and update Help Center articles. Separate Fin MCP exposes Fin as a callable support agent. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.

04 · Authentication and permissions

Official Intercom docs list 13 tools, OAuth or bearer-token authentication, US-hosted workspace limitation, Intercom API rate limits and read/write article scopes; do not conflate with inbound MCP connectors used by Fin. Official Intercom docs list 13 tools, OAuth or bearer-token authentication, US-hosted workspace limitation, Intercom API rate limits and read/write article scopes; do not conflate with inbound MCP connectors used by Fin.

05 · Monitoring, approval, and recovery

Official Intercom docs list 13 tools, OAuth or bearer-token authentication, US-hosted workspace limitation, Intercom API rate limits and read/write article scopes; do not conflate with inbound MCP connectors used by Fin. Official Intercom docs list 13 tools, OAuth or bearer-token authentication, US-hosted workspace limitation, Intercom API rate limits and read/write article scopes; do not conflate with inbound MCP connectors used by Fin.

06 · Gaps and implementation limits

Official Intercom docs list 13 tools, OAuth or bearer-token authentication, US-hosted workspace limitation, Intercom API rate limits and read/write article scopes; do not conflate with inbound MCP connectors used by Fin.

First-party MCP tool catalog

13 named MCP tools · Intercom remote server

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.

First-party exact listComplete list on cited pageIntercom MCP server
13 shown
Universal retrieval2
searchreadfetchread
Conversations and contacts4
search_conversationsreadget_conversationreadsearch_contactsreadget_contactread
Companies2
list_companiesreadget_companyread
Help Center articles5
list_articlesreadsearch_articlesreadget_articlereadcreate_articlewriteupdate_articlewrite
Catalog evidence: Intercom MCP server: available tools

First-party access

Documented surfaces

MCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceEvents / extensions ↗Webhooks, apps, or extensionsProduct ↗Native platform experience

Agent access

MCP and adjacent posture

Verified first-party provider MCPVendor-hosted remote Intercom data MCP plus distinct Fin Agent API MCPCurrent documented service

Role: provider

Read scope: Search and retrieve conversations, contacts, companies and Help Center articles; create and update Help Center articles. Separate Fin MCP exposes Fin as a callable support agent

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: Official Intercom docs list 13 tools, OAuth or bearer-token authentication, US-hosted workspace limitation, Intercom API rate limits and read/write article scopes; do not conflate with inbound MCP connectors used by Fin.

Approval boundary: Official Intercom docs list 13 tools, OAuth or bearer-token authentication, US-hosted workspace limitation, Intercom API rate limits and read/write article scopes; do not conflate with inbound MCP connectors used by Fin.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation5

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Intercom ships these experiences.

Single-platform patterns

  • Customer conversation and resolution cockpit
  • Account journey room
  • Pipeline-quality debugger
  • Customer expansion cockpit
Use in the brief composer →

Multi-platform compositions

  • Intercom + marketing or intent platform: account journey room
  • Intercom + conversation or support system + analytics or warehouse: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“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.

5 recorded sources
MCPRepresentative source
https://developers.intercom.com/docs/guides/mcp ↗

Official Intercom docs list 13 tools, OAuth or bearer-token authentication, US-hosted workspace limitation, Intercom API rate limits and read/write article scopes; do not conflate with inbound MCP connectors used by Fin.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

Developer docsSource inventory
https://developers.intercom.com/ ↗

First-party developer documentation or platform overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Webhooks / extensionsSource inventory
https://developers.intercom.com/docs/guides/webhooks ↗

First-party webhook, event, SDK, embedded-app, or extension documentation.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.intercom.com/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to the representative first-party source or targeted access review.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.