Intercom MCP server for AI agents.

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 231 Intercom actions across contacts, conversations, tickets and articles, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Intercom.

Intercom runs a remote MCP server for US and EU hosted workspaces (AU hosted workspaces are not yet supported), signed in with OAuth or an API token. Its tools are mostly reads, plus articles and internal notes. (Intercom's documentation, checked 22 October 2026.) Use Intercom's server when one person wants to work in Intercom from their own AI client. Use actionlake when you also want Intercom behind the same endpoint as your other systems: a key per agent with allowed actions and a spending cap, a named person's approval before destructive actions, a sealed record of every call, and one ask across Intercom and another system.

Intercom access token. Plus your region. The free call account { op: "connections.requirements", service: "intercom" } lists exactly what to paste.

Only if its key allows it, and only with an explicit confirmation. 40 Intercom actions are destructive, including delete a ticket, delete a contact and delete a company. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

actionlake paces every call to the limits in the Intercom service file: 1,600 calls per 10 seconds per connection. Repeated reads are answered from cache (110 Intercom actions can be), which never reaches Intercom.

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (231 Intercom actions page). Cache hits, searches, dry runs and calls Intercom refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

The Intercom REST API 2.16 (OpenAPI 3.0.1) at your region's intercom.io address, set when you connect. It is built from Intercom's documentation as read on 7 October 2026. 231 actions in 54 areas, each one in the signed service file (version 1.0.0).

Yes. ask joins Intercom to ConnectWise PSA or NetSuite on the same customer and returns the answer rather than every row. Intercom maps crm.company, which 227 other connectors also map.

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Intercom credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.