Intercom MCP ServerIntercom MCP Server
Intercom 官方托管 MCP server(闭源 remote,streamable-http):客服数据接进 AI 工具—— 14 工具:query-DSL search/fetch + conversations/contacts/companies 读 + Help Center articles 读写 + Fin Operator 五工具(apply_proposals 会真改线上配置;Bearer 连接拿不到 Operator 工具,要 OAuth)。 区域两口径:US/EU 端点分开(EU 数据在 EU 内处理)、AU 工作区不支持; 旧 SSE 端点已 deprecated。GitHub 那个仓只是文档仓,别当源码。
Intercom official hosted MCP server (closed-source remote, streamable-http): customer-support data plugged into AI tools — 14 tools: query-DSL search/fetch + reading conversations/contacts/companies + reading and writing Help Center articles + the five Fin Operator tools (apply_proposals really changes live workspace configuration; Bearer connections do not get the Operator tools — use OAuth). Two regional wordings: separate US/EU endpoints (EU data processed in the EU), AU workspaces unsupported; the legacy SSE endpoint is deprecated. That GitHub repo is documentation-only — don't mistake it for source.
适合与不适合When to use it, when not to
适合:支持团队把 Intercom 接进 Claude/Cursor/VS Code 等官方在册客户端;EU 数据驻留需求。 不适合:AU 托管工作区;要自托管/开源;要 Bearer 简单接入还用 Operator。
Fits: support teams plugging Intercom into Claude/Cursor/VS Code and other listed clients; EU data-residency needs. Not a fit: AU-hosted workspaces; self-hosted/open-source; Bearer simplicity while also using Operator.
中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-31
- 出品属地Origin
- 国外出品foreign-made Intercom Inc.(美国/爱尔兰双总部,客户消息平台)。Intercom Inc. (US/Ireland dual-headquartered customer messaging platform).
- 国内使用Direct access
- 大陆可直连direct OK developers.intercom.com 与 intercom.com 直连 200;mcp.intercom.com/mcp 与 mcp.eu.intercom.com/mcp 直连 401(端点存在需鉴权);mcp.intercom.com 首页直连 200(2026-10-31)。developers.intercom.com and intercom.com returned 200 direct; mcp.intercom.com/mcp and mcp.eu.intercom.com/mcp returned 401 direct (endpoints exist, auth required); the mcp.intercom.com landing page returned 200 direct (2026-10-31).
- 备案状态CAC filing
- 未见于备案名单not in filing list:未见于网信办公示名单(2026-10-31 检索);该产品未面向大陆公众提供服务,备案不适用。not in the CAC public registry (searched 2026-10-31); the product does not serve the mainland public, so filing does not apply.
备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准(按批次滚动更新,本站只抄编号不解读);「大陆可直连」是本站从大陆网络直连实测的结果,不是厂商承诺。GitHub 类站点当日实测有波动,口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.
固定坐标系Fixed coordinate system
11 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.
- 模型与开放条件Model & openness
它自己不调模型——官方托管远程 server,被 MCP 客户端调用。例外口径:Fin Operator 工具族 会驱动 Intercom 自家 AI(Operator)干活——send_operator_message 消耗 Operator credits (与在 Intercom 里开一轮对话同口径计费),其余四个 Operator 工具免费。
It calls no model itself — an official hosted remote server called by MCP clients. One exception wording: the Fin Operator tool family drives Intercom's own AI (Operator) to work — send_operator_message consumes Operator credits (billed the same way as starting a turn inside Intercom), while the other four Operator tools are free.
- 运行位置Where it runs
官方托管 remote server(无自托管线):US 端点 https://mcp.intercom.com/mcp、 EU 端点 https://mcp.eu.intercom.com/mcp(EU 请求在 EU 内处理,符合其 Regional Data Hosting 承诺); AU 托管工作区暂不支持(官方明写)。端点直连实测 401(存在、需鉴权,非死链)。
An official hosted remote server (no self-hosted line): the US endpoint https://mcp.intercom.com/mcp, the EU endpoint https://mcp.eu.intercom.com/mcp (EU requests are processed within the EU, in line with its Regional Data Hosting commitments); AU-hosted workspaces are not yet supported (stated plainly by the official docs). The endpoints measured 401 direct (they exist, auth required — not dead links).
- 本地文件Local files
不读写本机文件——读写对象全在 Intercom 工作区侧(conversations/contacts/companies/ Help Center articles)。
Reads and writes no local files — the read/write objects all live on the Intercom workspace side (conversations/contacts/companies/Help Center articles).
- 关机后的任务Tasks after shutdown
无常驻本机后台;连接活在客户端与 Intercom 托管端点之间(官方:连接保持活跃以接收更新)。
No persistent local background; the connection lives between the client and Intercom's hosted endpoint (official wording: the connection stays live to receive updates).
- 工具与扩展Tools & extensions
官方文档现口径 14 个工具:通用族 search(query DSL:object_type:conversations/contacts、 字段操作符 eq/neq/gt/contains、分页 starting_after)+ fetch(按前缀 ID 取全量详情); 直连 API 族 search_conversations / get_conversation / search_contacts / companies / Help Center articles(list/search/get 读 + create/update 写); Fin Operator 五工具(send_operator_message / get_operator_response / get_proposal_details / apply_proposals / reject_proposals——apply 会改动工作区线上配置)。
The current official-docs count is 14 tools: the universal family search (query DSL: object_type:conversations/contacts, field operators eq/neq/gt/contains, pagination via starting_after) + fetch (full details by prefixed ID); the direct-API family search_conversations / get_conversation / search_contacts / companies / Help Center articles (list/search/get read + create/update write); and the five Fin Operator tools (send_operator_message / get_operator_response / get_proposal_details / apply_proposals / reject_proposals — apply changes your workspace's live configuration).
- 上下文与记忆Context & memory
无 server 侧跨会话记忆;上下文=你的 Intercom 工作区数据本身(官方叙事:AI 助手保持 对工作区的环境感知)。Operator 对话有服务端会话态(get_operator_response 稍后取答)。
No server-side cross-session memory; the context is your Intercom workspace data itself (official narrative: AI assistants keep awareness of your workspace). Operator chats have server-side session state (get_operator_response collects the answer later).
- 权限与限制Permissions & limits
两种鉴权:OAuth(推荐;Dynamic Client Registration,但 redirect URI 过 allowlist—— localhost/127.0.0.1 任意端口已放行,其他回调要先申请加白)或 Bearer token(Intercom API token, 需 scopes:读 users/companies、读 conversations、读写 articles)。 Bearer 连接拿不到 Fin Operator 工具(官方明写);Operator 权限上线前建立的旧连接需重连。 工具按「你本人在工作区的权限」授权——MCP 不扩权。
Two authentication modes: OAuth (recommended; Dynamic Client Registration, but every registered redirect URI passes an allowlist — localhost/127.0.0.1 on any port is already allowed, other callbacks must be requested first) or Bearer token (an Intercom API token, with scopes: read users/companies, read conversations, read+write articles). Bearer connections do not get the Fin Operator tools (stated plainly by the official docs); connections made before the Operator permission existed must reconnect. Tools are authorized as you — mirroring your own workspace permissions, MCP grants no extra rights.
- 适合什么任务Best for
适合:客服/支持团队把 Intercom 数据接进 AI 工具(Claude/Cursor/VS Code 等官方在册客户端)—— 查会话、查联系人、读写帮助文档、驱动 Operator;EU 工作区有数据驻留线。 不适合:AU 托管工作区(不支持);要自托管/开源实现(无);要 Bearer 简单接入还用 Operator(拿不到)。
Fits: support teams plugging Intercom data into AI tools (Claude/Cursor/VS Code and other officially listed clients) — querying conversations and contacts, reading and writing Help Center docs, driving Operator; EU workspaces get a data-residency line. Not a fit: AU-hosted workspaces (unsupported); wanting a self-hosted/open-source implementation (none); wanting Bearer simplicity while also using Operator (you won't get it).
- 传输方式Transport
streamable-http(推荐:US https://mcp.intercom.com/mcp、EU https://mcp.eu.intercom.com/mcp) + legacy SSE(/sse,官方标 deprecated、仅为向后兼容保留)。核验:mcp.intercom.com 首页与 developers.intercom.com/docs/guides/mcp(2026-10-31 直连 200;端点直连 401=存在需鉴权)。
streamable-http (recommended: US https://mcp.intercom.com/mcp, EU https://mcp.eu.intercom.com/mcp) + legacy SSE (/sse, marked deprecated by the official docs, kept only for backwards compatibility). Verified: the mcp.intercom.com landing page and developers.intercom.com/docs/guides/mcp (200 direct on 2026-10-31; endpoints 401 direct = exist, auth required).
- 认证机制Authentication
OAuth(推荐;DCR+redirect URI allowlist)或 Bearer token(API token+scopes:读 users/companies、 读 conversations、读写 articles)。工具授权=你本人工作区权限镜像,MCP 不扩权。
OAuth (recommended; DCR + redirect-URI allowlist) or Bearer token (API token + scopes: read users/companies, read conversations, read+write articles). Tool authorization mirrors your own workspace permissions — MCP grants no extra rights.
- 权限范围Permission scope
读面(conversations/contacts/companies/articles)+ 写面(Help Center articles 创建/更新、 Operator apply_proposals 改线上配置);无本机面。写面按工作区权限与提案审批把关。
Read surface (conversations/contacts/companies/articles) + write surface (Help Center article create/update, Operator apply_proposals changing live workspace configuration); no local surface. The write surface is gated by workspace permissions and proposal approval.
头号误解Top misconception
- 把 inventory 旧 URL(intercom.com/mcp)当文档线——2026-10-31 实测 404;现役是 developers.intercom.com/docs/guides/mcp + 端点本身Treating the old inventory URL (intercom.com/mcp) as the docs line — measured 404 on 2026-10-31; the current line is developers.intercom.com/docs/guides/mcp plus the endpoint itself
- 把 intercom/intercom-mcp-server 仓当源码——它是文档仓(无 license、推送停 2025-09);server 闭源托管Treating the intercom/intercom-mcp-server repo as source — it is a documentation repo (no license, push stopped 2025-09); the server is closed-source hosted
- 用 Bearer token 却期待 Operator 工具——官方明写 Bearer 连接不含 Fin Operator 工具,要 OAuthUsing a Bearer token yet expecting Operator tools — the official docs state Bearer connections exclude the Fin Operator tools; use OAuth
- 混 US/EU 端点——app.intercom.com=US 用 mcp.intercom.com,app.eu.intercom.com=EU 用 mcp.eu.intercom.com;AU 不支持Mixing US/EU endpoints — app.intercom.com is US (mcp.intercom.com), app.eu.intercom.com is EU (mcp.eu.intercom.com); AU is unsupported
- 旧连接(Operator 权限上线前建的)调 Operator 工具报错——重连即可(官方排障口径)Old connections (built before the Operator permission) erroring when calling Operator tools — reconnect (official troubleshooting wording)
- 自建 MCP 客户端 OAuth 回调不在 allowlist——注册与授权会失败,localhost 之外要先申请Self-built MCP client OAuth callbacks not on the allowlist — registration and authorization fail unless localhost; otherwise request allowlisting first
- apply_proposals 会真改工作区线上配置——Operator 提案不是预览玩具apply_proposals really changes live workspace configuration — Operator proposals are not a preview toy
未知项清单Known unknowns
- 14 工具的完整参数面与分页游标语义细节(文档详尽但未逐条清点)
- Operator credits 的计费数值与配额(按 D9 与快照纪律不记数字)
- AU 工作区支持时间表(官方只说 not yet supported)
- The full parameter surface of the 14 tools and the pagination-cursor semantics in detail (the docs are thorough; not enumerated item by item)
- Operator credit pricing and quota numbers (per D9 and snapshot discipline no numbers are recorded)
- The support timeline for AU-hosted workspaces (the official docs only say not yet supported)
证据来源Evidence sources
判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-31,内容更新日content updated on 2026-10-31。
| 类型Type | 名称Name | 链接Link |
|---|---|---|
| docs | Intercom Developers · MCP 指南(14 工具清单/OAuth 与 Bearer/scopes/排障;直连 200)Intercom Developers · MCP guide (14-tool inventory / OAuth vs Bearer / scopes / troubleshooting; 200 direct) | https://developers.intercom.com/docs/guides/mcp |
| docs | mcp.intercom.com · 官方 MCP 首页(区域端点 US/EU、工具与分页口径;直连可达)mcp.intercom.com · official MCP landing page (regional US/EU endpoints, tool and pagination wording; reachable direct) | https://mcp.intercom.com/ |
| docs | Intercom · 官方集成页「Intercom MCP Server integration」(OAuth 口径/US 托管可用面/客户端名单)Intercom · official integration page "Intercom MCP Server integration" (the OAuth wording / US-hosted availability / client list) | https://www.intercom.com/integrations/connectors/intercom-mcp-server |
| repo | intercom/intercom-mcp-server · 文档仓(无 license;推送停 2025-09-22,GitHub API 核验;commits 作变更记录线)intercom/intercom-mcp-server · documentation-only repo (no license; last push 2025-09-22, GitHub API verified; commits as the change-record line) | https://github.com/intercom/intercom-mcp-server |
| changelog | GitHub commits · intercom-mcp-server(文档变更记录线)GitHub commits · intercom-mcp-server (documentation change-record line) | https://github.com/intercom/intercom-mcp-server/commits/main |
实测记录Measured runs
本档未在真实客户端逐项跑通;工具清单与权限来自官方 README。
This site has not completed measured runs. The test protocol is at protocols/mcp/_protocol.md.
相关条目Related entries
- Zapier MCPZapier MCP客服垂直 vs 千应用枢纽:Intercom 官方单产品深集成,Zapier 是跨应用入口。A customer-support vertical vs a thousand-app hub: Intercom is an official single-product deep integration, Zapier is a cross-application entry point.
- Atlassian MCPAtlassian Remote MCP Server(Jira/Confluence)同为 SaaS 官方 remote server:Atlassian 管工单/知识,Intercom 管客户会话与帮助中心读写。Both are official SaaS remote servers: Atlassian covers tickets/knowledge, Intercom covers customer conversations plus Help Center read-and-write.
- CursorCursor另一层 · AI 编程Other layer · AI coding
- Claude Code IDE 扩展Claude Code (IDE extension)另一层 · AI 编程Other layer · AI coding
本页由This page is generated from the ai-handbook 数据层生成(CC BY 4.0)。data layer (CC BY 4.0).
方法论与坐标系定义见仓库内For the methodology and coordinate definitions, see METHODOLOGY.md.