Available

Intercom MCP server

Work from an existing support conversation with Arc0’s Intercom tools. Keep internal notes separate from replies that message the customer immediately. Connect through Arc0 to use the actions your identity is allowed to call.

Customer supportAPI key · OAuthMCP + RESTintercom.com
AUDIT LOG · INTERCOMPOLICY: acme-support
09:41:07 · claude · u_8f2read
intercom.search_contacts
Search contacts✓ allowed · 212ms
09:41:08 · claude · u_8f2read
intercom.get_contact
Get contact✓ allowed · 164ms
09:41:09 · claude · u_8f2write
intercom.add_note
Add note✓ approved · approved by user
ILLUSTRATIVE POLICY TRACE · NOT A LIVE RECEIPT

Working with Intercom

Begin a support task with the conversation or contact ID already associated with the request. intercom.search_conversations can narrow discovery to that exact context, while intercom.get_conversation reads a bounded set of conversation parts. A truncated history should not be summarized as the entire exchange, and an absent message is not proof that it was never delivered.

Choose the write according to its audience. intercom.add_note records internal context for teammates. intercom.reply_conversation messages the customer immediately as the connected admin; it is not a draft. Neither action lets the caller impersonate another admin. Review the recipient context and response text before sending.

intercom.assign_conversation routes the conversation to another assignee, and intercom.close_conversation marks resolved work closed. Those changes can trigger notifications or automations. intercom.search_contacts and intercom.get_contact provide structural checks for known contacts rather than broad personal-data discovery. After an uncertain reply, read back the conversation and resolve the delivery status before another attempt, since repeating the call can send the customer a second message.

Official MCP reference: Intercom documentation.

01 · USE CASES

Agent workflows for Intercom.

01

Review a support thread

Use intercom.search_conversations for an exact contact or conversation and intercom.get_conversation for message context.

02

Send a reviewed reply

Use intercom.reply_conversation only when the response is ready to reach the customer now.

03

Leave internal context

Use intercom.add_note to record a handoff for teammates without messaging the customer.

04

Route resolved work

Use intercom.assign_conversation for reassignment and intercom.close_conversation when the request is resolved.

02 · ACTIONS

8 Intercom actions, graded by risk.

These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.

read

4

Look things up, subject to your permissions.

  • intercom.search_conversations
    Search conversations

    Use when finding conversations by exact id, contact id, or state. State searches enumerate workspace conversations; do not use them for person-scoped work. Returns structural summaries and a next cursor; fetch a known conversation for messages.

  • intercom.get_conversation
    Get conversation

    Use when reading a known support conversation before acting or reconciling an uncertain write. Returns up to 50 parts sorted by timestamp, undated parts last. Do not treat truncated history as complete or absence as proof a write failed.

  • intercom.search_contacts
    Search contacts

    Use when checking an exact contact id before support work. Empty results mean no match. Do not use for name/domain discovery or personal details.

  • intercom.get_contact
    Get contact

    Use when retrieving structural metadata for a known contact. A merged id may resolve to its survivor. Do not use for personal details or broad discovery.

write

4

Create and change things. Allow, or ask the user first.

  • intercom.reply_conversation
    Reply conversation

    Use when an approved reply should message the customer now as the connected admin from /me. Do not use for private notes or unsolicited outreach. No actor override. On any unknown write outcome, read back before retrying; absence is not proof of non-delivery.

  • intercom.add_note
    Add note

    Use when adding an internal note for teammates as the connected admin from /me. Does not message the customer. Do not use for customer replies. No actor override. On any unknown write outcome, read back before retrying.

  • intercom.close_conversation
    Close conversation

    Use when closing a resolved conversation as the connected admin from /me; no actor override. No customer message is added, but automations may notify participants. Do not close unresolved requests. On any unknown write outcome, read back before retrying.

  • intercom.assign_conversation
    Assign conversation

    Use when reassigning as the connected admin from /me; no actor override. May notify teammates or trigger automation. Do not use for customer replies. Assignee 0 unassigns. On any unknown write outcome, read back before retrying.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · POLICIES AND AUDIT

Control access to Intercom.

Connect the intended Intercom account, authorize your AI client and set policies for its tools.

Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.

Configure policies and approvals

Example policy choices

  • Read actions: allow where authorized
  • intercom.add_note: require approval

Arc0 MCP endpoint: https://api.arc0.ai/mcp

04 · AUTH AND DATA

How Intercom connects.

Connect Intercom using API key or OAuth. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →

AUTH
API key · OAuth
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · AI CLIENTS

Use Intercom with your AI client.

Sign in to Arc0 and connect Intercom in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.

Intercom with Claude

Claude Desktop + Claude Code

  1. In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
  2. For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
  3. Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Claude
Intercom with ChatGPT

ChatGPT on the web

  1. Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
  2. Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
  3. Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for ChatGPT
Intercom with OpenAI Codex

Codex app + CLI

  1. Run the registration command below. The app and CLI share ~/.codex/config.toml.
  2. Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
  3. Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for OpenAI Codex
Intercom with Cursor

Remote MCP setup

  1. Add Arc0 in your client’s remote MCP settings using the server URL below.
  2. Choose OAuth, sign in to Arc0, select the intended workspace and review access.
  3. Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Cursor
Intercom with VS Code

Remote MCP setup

  1. Add a remote HTTP MCP server named Arc0 using the URL below.
  2. Use OAuth and finish Arc0 sign-in, workspace selection and consent.
  3. Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
Intercom with Any MCP client

Streamable HTTP

  1. Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
  2. For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
  3. Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting

After setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.

07 · FAQ

Intercom and Arc0, answered.

Q01

Is there an official Intercom MCP server, and how does Arc0 differ?

Yes. Intercom documents a hosted MCP server. Arc0’s tools use a versioned REST action set and distinguish customer replies from internal notes under Arc0 policies.

Q02

Which permissions does Arc0 need for Intercom?

Public-app OAuth and private-workspace access tokens are supported. Permissions are read_conversations, write_conversations, read_users_companies and read_admins, selected in Intercom’s app configuration. Writes act as the admin identified by the connection.

Q03

Does this work with Claude, ChatGPT, Codex and Cursor?

Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.

Q04

How are credentials stored, refreshed and revoked?

Credentials are encrypted in Arc0’s vault. This OAuth flow has no scheduled refresh. An explicit disconnect attempts Intercom’s app-uninstall operation, which affects the workspace installation and may invalidate other connections using it. Failed connection attempts do not trigger uninstall. Check the installation in Intercom if remote cleanup fails.

Q05

What happens with rate limits or errors?

Intercom enforces API limits; Arc0 reports throttling and distinguishes invalid credentials from missing access. Conversation history is bounded. If a reply’s outcome is uncertain, absence from the returned excerpt does not authorize resending.

Q06

What is the availability of these Intercom tools?

These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.

Get started

Plug Intercom into your agent.

Intercom MCP server: 8 actions including search conversations, get conversation, reply conversation. Connect through Arc0.

Free to build · MCP + REST · Audit log on every plan

Intercom and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Intercom.