Skip to main content
Intercom is the connector to reach for when the question is about coverage: what customers are asking versus what your Help Center already answers.

What the agent gets

  • Conversations, searchable by source, author, state, tag, or date, with full message history on retrieval.
  • Contacts and companies, including custom attributes, plan, and spend.
  • Help Center articles, searchable by phrase and filterable by published or draft state.
  • Article drafting and updates, and internal notes on conversations, if you enable the write tools.
Typical uses: finding which rising contact drivers have no article behind them, then drafting the articles; pulling the account context behind a set of escalating conversations. If Intercom is already a Rippit integration, your conversations are in Rippit and you do not need this connector to analyze them. Connect Intercom when you want the agent to reach Help Center content, live contact and company records, or to write articles back.

Setup

Intercom accepts either a workspace access token or OAuth. Neither needs setup in Intercom beyond generating the token, if you choose that path. Workspace access token (recommended for shared use). Create one in Intercom and paste it into the connect dialog. It is stored encrypted and is not shown again. OAuth. Click connect and sign in to Intercom. Intercom’s hosted MCP server supports US and EU-hosted workspaces only.

Identity and scope

A workspace access token acts as the application rather than a person, org-wide, and does not break when someone leaves. That is the better fit for a connection a team relies on. When a write tool needs an author, Intercom attributes it per request. OAuth acts as the authorizing user and sees what that user sees.

Tools

The eleven read tools are enabled by default. The write tools are not.