Intercom MCP Server

Official Intercom-hosted remote MCP server for searching conversations and contacts, retrieving companies, and managing Help Center articles via AI assistants.

Communication by Intercom OAuth2 or Bearer Token active

Connect (Remote Server) GitHub Docs

Overview

The Intercom MCP server is an official, Intercom-hosted remote MCP endpoint that lets AI assistants securely access customer support data inside an Intercom workspace. It exposes conversations, contacts, companies, and Help Center articles through a standardized Model Context Protocol interface, so tools like Claude Desktop, Claude Code, Cursor, Windsurf, and VS Code can query and act on Intercom data without bespoke API code.

The server provides a universal search and fetch pair that uses a query DSL to find resources by type-prefixed IDs, plus direct API tools for conversations, contacts, companies, and articles (including create and update for articles). Authentication is handled either through an OAuth flow (recommended, browser-based) or a Bearer token using an Intercom API token. The server supports cursor-based pagination for search tools and page-based pagination for list tools, with up to 150 items per page.

Notable constraints: the server is currently only supported for US-hosted Intercom workspaces, and required OAuth scopes include reading users, companies, and conversations, plus read/write on articles. The implementation is hosted by Intercom at https://mcp.intercom.com/mcp (Streamable HTTP); an older SSE endpoint at https://mcp.intercom.com/sse is deprecated.

Tools

Tool	Description
`search`	Universal search tool for finding conversations and contacts using a query DSL with field-based operators.
`fetch`	Retrieve complete details for a specific resource using a type-prefixed ID.
`search_conversations`	Search conversations by IDs with filtering for source type, state, and assignment fields.
`get_conversation`	Retrieve a single conversation by ID with complete details.
`search_contacts`	Search contacts by IDs, name, email, phone, custom attributes, or domain.
`get_contact`	Get complete contact information including custom attributes.
`list_companies`	List companies with optional filtering by name, tag, or segment.
`get_company`	Retrieve complete company details.
`list_articles`	List Help Center articles with pagination.
`search_articles`	Search articles by phrase, state, or Help Center ID.
`get_article`	Retrieve complete article details including HTML body.
`create_article`	Create a new Help Center article with required title and author.
`update_article`	Update an existing article with new content or metadata.

Setup Guide

Prerequisites

An Intercom workspace hosted in the US region
Either OAuth login access to the workspace, or an Intercom API access token with the appropriate scopes (read users/companies, read conversations, read/write articles)
Node.js available locally to run npx mcp-remote

OAuth setup (recommended)

Add the following to your MCP client config (Claude Desktop, Cursor, VS Code, Windsurf, etc.):

{
  "mcpServers": {
    "intercom": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.intercom.com/mcp"]
    }
  }
}

On first use, a browser window will open to complete the OAuth flow against your Intercom workspace.

Bearer token setup

If you prefer a static API token, use this config:

{
  "mcpServers": {
    "intercom": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.intercom.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_INTERCOM_API_TOKEN"
      }
    }
  }
}

Replace YOUR_INTERCOM_API_TOKEN with an access token from your Intercom developer settings. After saving, restart your MCP client to load the server.

Use Cases

Triage support: pull all open conversations assigned to a teammate and summarize blockers
Customer research: look up a contact by email, fetch their conversation history, and surface recurring issues
Account intel: list companies in a segment and retrieve recent conversations tied to each
Help Center maintenance: search articles by phrase, update outdated content, or draft new articles from inside an AI assistant
Reporting: search conversations by state and source type to build a weekly support summary

Example Prompts

"Find all open conversations from contacts at acme.com and summarize the top three issues."
"Look up the contact with email jane@example.com and show me her last five conversations."
"List Help Center articles that mention 'SSO setup' and flag any in draft state."
"Create a new Help Center article titled 'Resetting your password' with this body, authored by user 12345."
"Update article 987654 to change the status to published and refresh the body."

Pros

Official, Intercom-hosted server with no infrastructure to run
OAuth support means no long-lived tokens required for most users
Covers the highest-value Intercom objects: conversations, contacts, companies, and articles (read and write)
Works across major MCP clients including Claude Desktop, Cursor, VS Code, and Windsurf

Limitations

Only supported for US-hosted Intercom workspaces at this time
Write access is limited to Help Center articles; conversations and contacts are read-only
Requires the mcp-remote shim because most clients do not yet speak Streamable HTTP natively

Alternatives

fabian1710/mcp-intercom: community MCP server focused on querying Intercom conversations
raoulbia-ai/mcp-server-for-intercom: community server geared toward analyzing support data
evolsb/fast-intercom-mcp: community server that caches Intercom data locally for faster analytics queries