Skip to content

Intercom

Artific Connect · Intercom gives a key Intercom's own tools: read conversations, contacts and companies, and read or write Help Center articles. It installs from the Marketplace like any other bundle.

What you get

One toolset, intercom, holding everything Intercom's own MCP server offers, plus a skill that tells the model what is read-only and what to confirm before writing an article.

What you supply at install

Intercom's remote MCP server does not admit a third party's own OAuth application the way GitHub's does, so this bundle asks for two things at install, both your organisation's own:

  • intercom_url — which of Intercom's two servers your workspace lives on: https://mcp.intercom.com/mcp for a US-hosted workspace, https://mcp.eu.intercom.com/mcp for an EU-hosted one. Check your workspace's own region before choosing; the two are separate systems and the wrong one answers nothing of yours.
  • intercom_token — your organisation's own Intercom access token, sent as the bearer credential on every call:
{ "type": "bearer", "secret": "<your Intercom access token>" }

Until both are supplied the subscription waits at needs configuration.

Before it works

Your administrator has to allow the host you chose (mcp.intercom.com or mcp.eu.intercom.com) in the key's own egress policy.

Good to know

  • Verified 2026-09-24 on developers.intercom.com/docs/guides/mcp: the two server paths, the US/EU split, and that a static access token is an offered alternative to the OAuth flow.
  • Not verified: the exact API-token scopes the token needs; Intercom's docs describe the granted categories (read users and companies, read conversations, write conversations for internal notes, read and write articles) without naming discrete scope identifiers.
  • AU-hosted workspaces are not supported by Intercom's MCP server at all, per the same page.
  • The mark: this bundle's card still uses Artific's own placeholder. Intercom's own trademark guidelines permit the mark for exactly this purpose ("to accurately illustrate how your product ... works with the Intercom product"), but the only official asset this deployment could reach without a Brandfolder session was a 32×32 favicon, too small to scale into a card cleanly (checked 2026-09-24).