跳过安装。2 分钟内即可运行。
在 cloud.anythingmcp.com 开始免费试用，一键添加 Intercom，然后将你的 AI 客户端（Claude、ChatGPT、Copilot 或 Cursor）指向生成的 MCP 端点。无需 Docker，无需 git clone，无需任何工程经验。
摘要
让你的 AI 在 Intercom 中工作：查找和更新联系人与公司，阅读、搜索和分拣会话与工单（回复、添加备注、分配、暂缓、关闭、打标签），并管理 Help Center 的文章和集合。支持美国、欧盟或澳大利亚的工作区，使用 Developer Hub 应用的访问令牌。
试试这样问
Intercom 的示例提示
点击任意提示即可复制，然后粘贴到 Claude、ChatGPT、Cursor、Gemini、Copilot 或 OpenClaw 中，在该连接器上运行。
Intercom · 通过 MCP 实时
分享Claude 是 AI，可能会出错。请核对回答。
💡 无需安装? 直接使用 cloud.anythingmcp.com。 登录、点击 Connectors → Intercom、粘贴凭证、生成 MCP API key，即可完成。无 Docker、无
git clone、无本地服务器。
Intercom + Gemini
让你的 AI 在 Intercom 中工作：查找和更新联系人与公司，阅读、搜索和分拣会话与工单（回复、添加备注、分配、暂缓、关闭、打标签），并管理 Help Center 的文章和集合。支持美国、欧盟或澳大利亚的工作区，使用 Developer Hub 应用的访问令牌。
前提条件
完整的设置说明已内置在连接器中 (在 store 中选择连接器时可见)。所需环境变量:
INTERCOM_API_URL, INTERCOM_ACCESS_TOKEN
步骤 1 — 获取凭证
- 以管理员身份登录你的 Intercom 工作区，打开 Developer Hub：
https://app.intercom.com/a/apps/_/developer-hub（或 Settings → Integrations → Developer Hub）。欧盟和澳大利亚的工作区在 app.eu.intercom.com 或 app.au.intercom.com 上使用相同路径。 - 点击 New app，为应用命名（例如 AnythingMCP），选择工作区，然后点击 Create app。应用会立即安装到该工作区：你自己的工作区不需要 OAuth，也不需要应用审核。
- 打开应用的 Configure → Authentication 页面。这里显示工作区的 Access token 及其拥有的权限。要使用全部工具，请授予 users 和 companies、conversations、tickets、articles 的读写权限，再加上 Read admins、Read tags 和 Write tags。修改权限后，请重新生成令牌并使用新令牌。
- 把令牌粘贴到
INTERCOM_ACCESS_TOKEN，不要带 Bearer 一词。请像对待密码一样对待它：它可以打开你工作区的客户数据。 - 按工作区所在区域设置
INTERCOM_API_URL：https://api.intercom.io（美国，你使用 app.intercom.com）、https://api.eu.intercom.io（欧盟，app.eu.intercom.com）或https://api.au.intercom.io（澳大利亚，app.au.intercom.com）。 - 安装连接器并运行
intercom_get_me。它会返回你的管理员 id 以及工作区和所在区域。
试用：从 https://app.intercom.com/admins/sign_up/developer 创建的免费开发工作区就足够了。它位于美国区域，不发送邮件或推送通知，最多容纳 20 个 users 和 leads，并且永远不能转为正式工作区。
只读设置：只授予读取权限（Read and list users and companies、Read conversations、Read tickets、Read and List articles、Read admins、Read tags），并关闭写入类工具。三个搜索工具只做读取。
以管理员身份操作：回复、备注、分配、暂缓、关闭和重新打开都会记在某位团队成员名下，新文章也是如此。intercom_get_me 可以找到你自己的管理员 id，intercom_list_admins 可以找到其他团队成员。
先确认：在会话中回复、comment 类型的工单回复、带消息关闭会话以及发布文章，都会送达客户；修改已发布的文章会立即生效。AI 会先把文本给你看，等你同意后再执行。备注只在团队内部可见，新文章以草稿形式创建。intercom_delete_contact、intercom_delete_article 和 intercom_delete_collection 在安装时默认关闭；隐藏联系人的可撤销方式是 intercom_archive_contact。
限制：默认每个应用每分钟 10,000 次调用，每个工作区每分钟 25,000 次，按 10 秒窗口分配。返回 429 时请等待几秒。
常见错误：401：令牌错误或已重新生成、应用已被卸载，或者 INTERCOM_API_URL 与工作区所在区域不符。403：令牌缺少某项权限，或者你的套餐不包含该功能（例如工单）。工单返回 404 通常表示用了 Inbox 中的编号，而不是工单 id。410：该联系人已被合并到另一个联系人，请按邮箱搜索保留下来的联系人。
该连接器不会发起外发消息，不会创建会话或工单，不会删除会话或合并联系人，也不涉及 data events、news items、宏、Fin、custom objects、通话、数据导出、Webhook 和工作区设置。
步骤 2 — 安装 adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
步骤 3 — 在 Gemini 中添加连接器
你的服务器 URL： 在 AnythingMCP 中打开 MCP Servers → 此连接器所在的服务器，复制它的 URL（
https://cloud.anythingmcp.com/mcp/…）。本指南中出现YOUR_SERVER_ID的地方都用它替换。
Gemini CLI 从 ~/.gemini/settings.json（Windows 上为 %USERPROFILE%\.gemini\settings.json）读取 MCP 服务器。添加：
{
"mcpServers": {
"anythingmcp": {
"httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
"headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
}
}
}
- 在 AnythingMCP 的 MCP Servers → 你的服务器 → API keys 中创建 MCP API 密钥，并用它替换
YOUR_MCP_API_KEY。 - 保存文件并重启
gemini。 - 在 Gemini CLI 中运行
/mcp（或在终端运行gemini mcp list），anythingmcp应显示为已连接。 - 开始输入提示，Gemini CLI 现在可以调用
Intercom的工具。
可用工具
| Tool | What it does |
|---|---|
intercom_get_me | Read who the access token belongs to: the admin id, name and email, plus the workspace (app) with its id_code, name, timezone and region |
intercom_list_admins | List the workspace admins (teammates) with id, name, email, away_mode_enabled, has_inbox_seat and team_ids |
intercom_get_admin | Read one admin (teammate): name, email, away mode and reason, inbox seat and the ids of their teams |
intercom_list_teams | List the workspace teams with id, name and admin_ids |
intercom_get_team | Read one team: name, the ids of its admins, the assignment limit and the distribution method |
intercom_list_tags | List every tag in the workspace with id and name |
intercom_create_tag | Create a tag, or return the existing tag with that name (names are case-insensitive) |
intercom_list_segments | List the saved contact and company segments with id, name, person_type and dates, optionally with how many contacts each holds |
intercom_list_data_attributes | List the data attributes of contacts and companies, standard and custom: name, full_name (the field name to use in searches and updates)… |
intercom_list_contacts | List contacts (users and leads), newest first, with id, role, email, name, phone, external_id, owner_id, location, timestamps and… |
intercom_search_contacts | Search contacts by their attributes, e.g. email, name, phone, external_id, role (user or lead), created_at, last_seen_at, tag_id… |
intercom_get_contact | Read one contact: role, email, phone, name, external_id, owner_id, location, browser and device, unsubscribe and bounce flags, timestamps… |
intercom_find_contact_by_external_id | Find a user by the external_id your own system gave them (users only, not leads) |
intercom_create_contact | Create a contact, a user or a lead |
intercom_update_contact | Change a contact: only the fields given are overwritten |
intercom_archive_contact | Archive a contact: it disappears from lists, searches and the Inbox until unarchived with intercom_unarchive_contact |
intercom_unarchive_contact | Bring an archived contact back, so it shows again in lists, searches and the Inbox |
intercom_delete_contact | Delete a contact for good, with their data |
intercom_list_contact_tags | List the tags on one contact with id, name, applied_at and who applied them |
intercom_tag_contact | Put an existing tag on a contact (intercom_create_tag makes a new one) |
intercom_untag_contact | Take a tag off a contact; the tag itself stays in the workspace |
intercom_list_contact_notes | List the internal notes teammates left on a contact, newest first, with id, body (HTML), created_at and author |
intercom_add_contact_note | Leave an internal note on a contact |
intercom_list_contact_companies | List the companies a contact belongs to, with id, company_id, name, plan, user_count, monthly_spend and custom_attributes |
intercom_attach_contact_to_company | Add a contact to a company |
intercom_detach_contact_from_company | Remove a contact from a company; both stay in the workspace |
intercom_list_companies | List companies, or find one by name or by your own company_id, or filter by tag or segment |
intercom_get_company | Read one company by the id Intercom gave it: company_id, name, plan, size, website, industry, user_count, session_count, monthly_spend… |
intercom_create_or_update_company | Create a company, or update the one that already has this company_id (your own id for it, which cannot be changed later) |
intercom_list_company_contacts | List the contacts that belong to a company, with id, role, email and name |
intercom_list_conversations | List conversations, most recently updated first, with id, title, state (open, closed, snoozed), open, read, priority, admin_assignee_id and… |
intercom_search_conversations | Search conversations, e.g. by open, state (open, closed, snoozed), admin_assignee_id, team_assignee_id, contact_ids, tag_ids, priority… |
intercom_get_conversation | Read one conversation with its messages: state, assignees, contacts, tags, priority, statistics and conversation_parts (replies, notes… |
intercom_reply_to_conversation | Reply to a conversation as an admin |
intercom_add_conversation_note | Add an internal note to a conversation |
intercom_assign_conversation | Assign a conversation to an admin or to a team (a conversation can have both), or unassign it with assignee_id "0" |
intercom_close_conversation | Close a conversation (intercom_open_conversation reopens it) |
intercom_snooze_conversation | Snooze a conversation until a time; it reopens by itself then |
intercom_open_conversation | Open a closed or snoozed conversation again, so it is back in the Inbox |
intercom_tag_conversation | Put an existing tag on a conversation (intercom_create_tag makes a new one) |
intercom_untag_conversation | Take a tag off a conversation; the tag itself stays in the workspace |
intercom_search_tickets | Search tickets, e.g. by ticket_type_id, open, state, title, description, category (request for customer tickets, task for back-office… |
intercom_get_ticket | Read one ticket: id, ticket_id (the Inbox number), ticket_attributes (title, description and custom ones), ticket_state, ticket_type… |
intercom_reply_to_ticket | Reply to a ticket as an admin. message_type note stays internal; comment is shown to the customer: show the text and confirm with the user… |
intercom_update_ticket | Change a ticket: its attributes (title, description, custom ones), state, assignee, open or closed, snooze, sharing with the customer |
intercom_list_ticket_types | List the ticket types with id, name, category (Customer, Back-office, Tracker), archived and their ticket_type_attributes (name, data_type… |
intercom_list_ticket_states | List the ticket states with id, category (submitted, in_progress, waiting_on_customer, resolved), internal_label, external_label and the… |
intercom_list_help_centers | List the Help Centers of the workspace with id, identifier, display_name, url, custom_domain and whether the website is on |
intercom_list_collections | List Help Center collections and sections, most recently updated first, with id, name, description, url, parent_id (set on sections and… |
intercom_get_collection | Read one Help Center collection: name, description, url, icon, order, parent_id, help_center_id and translated_content |
intercom_create_collection | Create a Help Center collection, or a sub-collection with parent_id |
intercom_update_collection | Rename a Help Center collection, change its description or move it under another parent |
intercom_delete_collection | Delete a Help Center collection for good |
intercom_list_articles | List Help Center articles, most recently updated first, with id, title, description, body (HTML), author_id, state (published or draft)… |
intercom_search_articles | Search Help Center articles for a phrase |
intercom_get_article | Read one Help Center article: title, description, body (HTML), author_id, state, parent_ids, url, statistics and translated_content per… |
intercom_create_article | Write a new Help Center article |
intercom_update_article | Change a Help Center article |
intercom_delete_article | Delete a Help Center article for good; setting state draft with intercom_update_article only unpublishes it |
示例提示
- “列出所有尚未分配给任何人的未结会话，并注明每个会话的客户和主题。”
- “找到邮箱为 [email protected] 的联系人，汇总她所属的公司、标签和最近的会话。”
- “为关于账单的最早一条未结会话起草回复，发送前先给我看。”
- “列出 Help Center 中仍是草稿的文章，并告诉我哪些看起来可以发布了。”
FAQ
Gemini CLI 从哪里读取 MCP 服务器？ 用户级配置位于 ~/.gemini/settings.json，项目级配置位于项目内的 .gemini/settings.json。gemini mcp list 会列出每个服务器及其连接状态。
下一步
这份指南对你有帮助吗?
