If you're searching for "Intercom MCP", you're asking one of two things: does Intercom have an MCP server? or how do I connect Intercom to an AI assistant via the Model Context Protocol?
⚠️ No official Intercom MCP server yet. Community options exist — details below.
What Is MCP?
Model Context Protocol (MCP) is an open standard developed by Anthropic that lets AI assistants — like Claude — connect to external tools, APIs, and data sources in a standardised way.
Before MCP, every AI integration required bespoke tooling: custom prompts, custom API wrappers, and custom glue code to pass context back and forth. MCP replaces that with a common interface: the AI asks the MCP server for data or actions, the server returns structured results, and the AI uses them to answer your question or complete a task.
In plain terms: MCP is how you give an AI assistant live access to Intercom — not just knowledge about it, but real, up-to-date data from your account.
What a Intercom MCP Integration Does
Once Intercom is connected via MCP, your AI assistant can:
- Read live data — pull records, metrics, activity, and status directly from Intercom
- Take actions — create, update, or log records based on your instructions
- Cross-reference context — combine Intercom data with other connected tools mid-conversation
The key difference from a standard chatbot: the assistant is not working from training data or memory. It is reading your actual Intercom instance, in real time.
Practical Intercom MCP Use Cases
Ticket lookup and context before replying
Before drafting a reply, the assistant fetches the ticket history and account context from Intercom — so the draft references the right details.
Churn risk flagging
Ask the assistant to identify customers with multiple open tickets or declining activity in Intercom, and produce a prioritised list for the CS team to review.
Macro and template generation
Have the assistant draft new macros or canned responses based on common ticket patterns it reads directly from Intercom.
How to Connect Intercom via MCP
There are two main paths:
Option A: Use a community MCP server for Intercom
Intercom does not currently maintain an official MCP server. Community-built options exist — check the MCP Registry and GitHub for the latest.
Note: No official Intercom MCP server yet. Community-built options exist — check the MCP Registry for current options.
What you'll need:
- An MCP-compatible client (Claude Desktop, OpenClaw, or another host)
- A running MCP server process with Intercom credentials configured
Community servers vary in completeness and maintenance quality — evaluate before deploying to your team.
Option B: Use Cody (OpenClaw-based, managed)
Cody is built on OpenClaw and supports MCP-compatible integrations out of the box. You connect Intercom once from the Cody dashboard — no server to run, no code to write — and Cody handles authentication, context passing, and write-back actions with appropriate guardrails.
Cody works where your team already operates: Slack, Telegram, or the web chat. The Intercom connection is available to your entire team without each person setting up their own MCP client.
Want Intercom Connected to AI Without Running Your Own MCP Server?
Cody has Intercom integration built in. Get conversation context and inbox health in Slack without access token setup.
MCP vs Other AI Integration Patterns
| Approach | What it is | Tradeoff |
|---|---|---|
| MCP | Standardised protocol for live tool access | Requires an MCP server; most powerful when set up correctly |
| RAG (retrieval) | Pre-index Intercom content and retrieve it | Good for static docs; not suitable for live/transactional data |
| Manual copy-paste | Paste Intercom output into ChatGPT/Claude | Fast to start; breaks for anything recurring or at scale |
| Custom API wrappers | Bespoke integration code per tool | Full control; high maintenance overhead |
MCP wins when you need live data from Intercom and want to avoid rebuilding integrations as APIs change.
Common Mistakes
- Using training data when live data is needed — if the AI doesn't have an MCP connection, it will answer from memory, which is often outdated or wrong for account-specific questions
- No write-back guardrails — MCP can write to Intercom, so it's worth adding an approval step for any action that modifies records
- Too many tools exposed at once — give the AI access to the Intercom actions it actually needs; a scoped connection is easier to reason about and audit
- Skipping structured outputs — ask the AI to return structured JSON or clear fields when writing back to Intercom; free-form output is harder to validate
Related MCP Guides
Want the full workflow picture? See: Intercom AI Automation and How to Connect Intercom to OpenClaw.