Source verified. Facts shown were checked against the linked official source. Source verified does not mean that ACCircuit operationally tested this capability or endorses it. ACCircuit does not verify security, performance, availability, or fitness for a particular use.

Unclaimed directory record. ACCircuit does not represent or endorse this provider.

ACCircuit has not operationally tested security, performance, availability, or fitness for a particular use.

Intercom MCP server

Provides a remote MCP connection for authorized AI clients to work with Intercom customer-support context and actions.

Delivery

Remote MCP server

Supported buyer outcomes

Works with

  • Intercom workspaces
  • MCP-compatible AI clients

Includes

  • Authorized Intercom context
  • Customer-support data access
  • Supported Intercom actions

Capability circuit

Connect a compatible client → Authorize the Intercom workspace → Request support context → Review any proposed action

Source and review record

Evidence

Source facts

  • Intercom MCP guide

    Intercom's official guide content supports a remote MCP connection for authorized customer-support context and actions.

    Retrieved
    2026-08-12
    Limitation
    The editorial fetch path failed on 2026-08-11; a controller confirmed HTTP 200 with Node and Windows system CAs on 2026-08-12. Neither path tested MCP operation.
    Provenance
    Source record

Editorial estimates

No editorial estimates are recorded.

Buyer assumptions

No buyer assumptions are recorded.

Record details

Asset form
mcp
Platform
Web
Maintenance owner
shared
Access method
Remote MCP
Commercial status
Not confirmed
Last reviewed
2026-08-11
Provider
Intercom

Requirements

  • An authorized Intercom workspace
  • An MCP-compatible AI client

Verification scope

Reviewed the official Intercom guide's indexed content and independently confirmed the exact guide URL returned HTTP 200 through Node using Windows system CAs on 2026-08-12.

Limitations

  • ACCircuit reviewed the official source description only; it did not run the capability or verify security, performance, or availability.
  • ACCircuit's editorial web fetch returned an internal error on 2026-08-11; the separate HTTP 200 check was source reachability only, not an MCP operation.

Visit official source · Claim or correct this record