Intercom
by Intercom
Search customer conversations, contacts, companies and Help Center articles from your AI agent. Intercom documents 13 tools — two of which create and update live Help Center articles, despite Anthropic's directory labelling the connector Read.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Intercom via MCP
https://mcp.intercom.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect Intercom once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioIntercom Tools & Capabilities (13)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The directory listing is a subset, not the surface. Six names against 13 documented, omitting the entire company and Help Center groups, including both writes. An integration planned from the snapshot will be missing more than half the tools.
- The
Readpermissions label is inaccurate. Two documented tools create and update live Help Center content. Do not treat the label as a technical guarantee of read-only behaviour. - We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no safety annotations were readable and no schema-level detail is published here.
- No scopes are advertised over the wire. Intercom's RFC 8414 document carries no
scopes_supportedkey, and its RFC 9728 protected-resource descriptor is not served at any of the three standard path forms. The required permissions exist only as prose in the guide. - Australia-hosted workspaces are unsupported. Intercom states this plainly; there is no AU endpoint.
- The SSE endpoint is deprecated. Intercom marks the legacy
/ssetransport deprecated in the same table where it publishes it. Build on Streamable HTTP. - Rate limits are the REST API's, and they are workspace-wide. 10,000 calls a minute per app and 25,000 per workspace, so a busy agent competes with every other integration on the workspace. Intercom's MCP troubleshooting offers no MCP-specific limit, only advice to slow down.
- Pagination defaults are small. Search tools default to 5 results and cap at 150 per page, so an agent surveying a large inbox must walk cursors rather than pull one big set.
- Prompts are unknown, not absent. Anthropic's directory snapshot records an empty
prompt_nameslist, and the gated endpoint means we could not runprompts/listto check whether the server serves any.
Frequently asked questions
It can write. Intercom's own MCP guide documents `create_article` and `update_article`, which create and update articles in your live Help Center. Anthropic's directory snapshot labels the connector Read and lists only six read tools, so the label understates the surface. Intercom's required-scopes list confirms it, asking for read and write access to articles.
Intercom documents 13 tools; Anthropic's directory snapshot names only six. The seven the snapshot omits are `list_companies`, `get_company`, `list_articles`, `search_articles`, `get_article`, `create_article` and `update_article` — the whole Help Center and company surface. Treat Intercom's own guide as authoritative and the directory listing as an out-of-date subset.
They are the generic deep-research pair, adapted to Intercom. Intercom calls them universal tools: `search` takes a query DSL string and requires an object type of conversations or contacts, returning summary results with type-prefixed IDs. You then pass one of those IDs to `fetch`, which returns full details including conversation parts and custom attributes.
Intercom names three permission groups rather than machine-readable scope strings. Its MCP guide asks for read and list users and companies, read conversations, and read and write articles. Those match checkbox labels in Intercom's OAuth scopes reference. The server's own RFC 8414 metadata publishes no scopes_supported key at all, so no scope list is advertised over the wire.
Yes, on a different endpoint. Intercom hosts the MCP server for both US and EU workspaces, and EU requests are processed within the EU under its regional data hosting commitments. Use `https://mcp.eu.intercom.com/mcp` for EU workspaces, which Anthropic's directory does not list. Australia-hosted workspaces are not supported yet.
Either works. Intercom's guide documents two authentication approaches and recommends the browser-based OAuth flow. The alternative is passing an existing Intercom access token as a bearer header. If you take the token route, Intercom warns that the token itself must already carry the permissions listed above, or tools fail on authorization rather than on connection.
Intercom's REST API limits apply, because the tools call that API. Intercom documents a default of 10,000 calls per minute per app and 25,000 per minute per workspace, for both private and public apps. Exceeding them returns HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining and reset headers. Intercom's own MCP troubleshooting advice is simply to reduce request frequency.
Sources
- Intercom MCP guide — https://developers.intercom.com/docs/guides/mcp (fetched 2026-08-19 as Markdown via the
.mdsuffix) · retrieved 2026-08-19 - Intercom OAuth Scopes reference — https://developers.intercom.com/docs/build-an-integration/learn-more/authentication/oauth-scopes (fetched 2026-08-19 as Markdown) · retrieved 2026-08-19
- Intercom REST API rate limiting — https://developers.intercom.com/docs/references/rest-api/errors/rate-limiting (fetched 2026-08-19 as Markdown) · retrieved 2026-08-19
- Intercom Regional Data Hosting — https://www.intercom.com/help/en/articles/6124430-regional-data-hosting (linked from the MCP guide; not separately fetched)
- Intercom docs machine index — https://developers.intercom.com/llms.txt (fetched 2026-08-19; also names the sitemap at https://developers.intercom.com/sitemap.xml, fetched 2026-08-19) · retrieved 2026-08-19
www.intercom.com/robots.txtdisallows only/api/,/assets/books,/early-stage/*,/blogtest,/beta/*,/roi/*and/drlp-v2/*, and carriesContent-Signal: ai-train=yes, ai-input=yes, search=yes— synthesis is expressly permitted on all three axes (fetched 2026-08-19).developers.intercom.com/robots.txtreturns the site's single-page-app HTML shell rather than a robots file, so no separate policy is published for the docs host. · retrieved 2026-08-19- Live RFC 8414 authorization-server metadata — https://mcp.intercom.com/.well-known/oauth-authorization-server (fetched 2026-08-19; the path-insert and path-append forms return 404 and 401 respectively) · retrieved 2026-08-19
- Live RFC 9728 probe — all three path forms tried 2026-08-19; no protected-resource descriptor is served · retrieved 2026-08-19
- Live anonymous probe — 2026-08-19: an MCP POST to the endpoint returns HTTP 401 with
www-authenticate: Bearer realm="OAuth"· retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/b2def8dc-ae47-4d46-877a-19b6a6ebb771 (snapshot 2026-08-16) · retrieved 2026-08-16
- Intercom support — https://www.intercom.com/help · Privacy — https://www.intercom.com/legal/privacy
Server Info
- Category
- Communication
- Developer
- Intercom
- Tools
- 13
- Domain
- mcp.intercom.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Communication
Related Resources
Ready to connect Intercom?
Connect Intercom once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.