Intercom MCP Server – Conversations and Contacts

Intercom's official hosted MCP server gives AI assistants secure access to customer-support and workspace data, including conversations, contacts, companies, and Help Center articles. Use it to retrieve context, search records, and manage approved knowledge-base content from an MCP-compatible client.

#customer-support#conversations#knowledge-base

Overview

Intercom's official MCP server connects compatible AI assistants to an
Intercom workspace through a hosted, authenticated remote service. It gives an
agent structured access to current customer-support data and selected Help
Center actions instead of relying only on manually pasted conversation text or
static model knowledge.

What the MCP server enables

Intercom documents 13 tools covering universal search, direct retrieval, and
selected content-management actions. Depending on the authenticated user's
permissions and token scopes, an AI agent can:

Search conversations and contacts with field-based filters and free text.
Retrieve complete conversation, contact, and company details.
List companies and filter them by name, company ID, tag, or segment.
List, search, and retrieve Intercom Help Center articles.
Create new Help Center articles.
Update existing Help Center articles.
Follow pagination across large contact, conversation, company, and article sets.
Return direct links to relevant records in the Intercom application.

When to use it

Use Intercom MCP when an AI workflow needs live customer-support context or
must perform an approved knowledge-base action. Typical workflows include
finding open conversations about a product issue, retrieving a customer's full
profile, reviewing companies in a segment, locating relevant Help Center
content, drafting a new support article, or updating an existing article after
a product change.

Connection and authentication

Intercom recommends Streamable HTTP at
https://mcp.intercom.com/mcp. The server also keeps
https://mcp.intercom.com/sse as a deprecated legacy endpoint for backwards
compatibility.

Authentication supports an interactive OAuth flow or a bearer API token.
Clients that cannot connect directly to a remote MCP server can use the
documented mcp-remote stdio bridge. Bearer-token access must include the
required scopes for users and companies, conversations, and article read/write
operations.

Key considerations

The service is currently supported only for US-hosted Intercom workspaces.
Access remains limited by the authenticated user's permissions and token scopes.
Intercom API rate limits still apply, and search and list tools paginate results.
Use least privilege, keep tokens in protected environment variables, and require
human confirmation before creating or updating Help Center articles. Prefer
Streamable HTTP for new integrations and use SSE only for older clients that
cannot yet support the recommended transport.

Frequently Asked Questions

When should an AI agent use the Intercom MCP server?

Use it when a workflow needs current Intercom workspace context or approved support-content changes, such as searching customer conversations, retrieving contact or company details, finding Help Center articles, or creating and updating knowledge-base content.

What does the Intercom MCP server add to an AI agent's capabilities?

It gives the agent structured access to live Intercom conversations, contacts, companies, and Help Center tools, allowing it to retrieve and act on current workspace information instead of relying only on static model knowledge or manually pasted records.

What can an AI agent access or manage through Intercom MCP?

Depending on permissions and scopes, the agent can search and retrieve conversations and contacts, retrieve company details, list companies, list and search Help Center articles, and create or update articles.

How is authentication configured for the Intercom MCP server?

The hosted server supports interactive OAuth or a bearer API token. Bearer tokens must include the scopes required for users and companies, conversations, and article read/write access. Store tokens securely and do not place real credentials directly in the YAML.

Which transport should be used for the Intercom MCP server?

Use Streamable HTTP at https://mcp.intercom.com/mcp for modern clients. Use the SSE endpoint only for backwards compatibility, or the documented mcp-remote stdio bridge when the client cannot connect directly to a remote MCP server.