Intercom MCP Server: What It Does and How to Connect Intercom to AI in 2026
Yes — Intercom has an official MCP server. It’s hosted at mcp.intercom.com, and it lets any MCP-compatible AI tool search and read your conversations, contacts, companies, and help center articles, plus create and update articles. If you’re searching “Intercom MCP,” the connection exists and it’s maintained directly by Intercom.
The thing worth knowing before you set it up: an MCP server hands your support data to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches Intercom for you, nothing fires when a conversation comes in or a ticket goes cold, and nothing runs while the chat is closed. Here’s exactly what the Intercom MCP does, how to turn it on, where it stops — and what to use when you want Intercom work that runs on its own.
What the Intercom MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, and others — talk to an outside app through a shared interface. Intercom maintains one official server, reachable at https://mcp.intercom.com/mcp, with 13 tools. Most are read-only:
- Search and fetch — a universal search tool plus dedicated lookups for conversations, contacts, companies, and articles.
- Conversations — search by state, source, author, or timing, then pull a full conversation with all its parts and metadata.
- Contacts and companies — search by ID, name, email, phone, custom attributes, or email domain; list and inspect companies.
- Help center articles — search and read existing articles, and (the one write path Intercom exposes) create or update an article.
With it connected, an AI client can:
- Pull a conversation — “show me the last exchange with this customer” answered from live Intercom data.
- Search for patterns — “find open conversations mentioning refunds from the last week.”
- Draft or fix help content — update an outdated help center article on the spot.
It’s genuinely useful for ad-hoc digging: ask a question about a customer or conversation, get an answer grounded in real Intercom data, right inside the chat. Note the current constraint: Intercom’s docs say the MCP server only supports US-hosted workspaces for now.
How to set up the Intercom MCP server
The official server is the quick path — no code, no separate hosting:
- In your AI client’s connector settings, add a remote MCP server pointing at
https://mcp.intercom.com/mcp(the older/sseendpoint still works but is deprecated). - Authenticate — Intercom supports OAuth (automatic, browser-based) or a bearer token if you’d rather authenticate directly with an API key.
- Confirm the tools appear in the client, then start a chat and ask it to search a conversation or contact.
That’s the whole setup for a US-hosted workspace. If your workspace is hosted outside the US, the official server currently isn’t available to you, and you’d be looking at a community MCP server instead — worth treating with more caution since it isn’t maintained or verified by Intercom.
Where the Intercom MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch Intercom; it waits for you to ask.
- No triggers. A new conversation coming in, a customer going quiet, an SLA about to breach — none of these can start anything through MCP. There’s no “when this happens in Intercom, do that.”
- It’s one app at a time. The Intercom MCP knows Intercom. Getting a resolved conversation’s details into your CRM, a Slack channel, and a spreadsheet means wiring up (and authing) a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the plumbing and the scopes. OAuth tokens, refresh, and the blast radius of read access to customer conversations and contacts are all on you.
So the Intercom MCP is a great way to ask Intercom things and make the occasional article edit. It is not a way to make Intercom run — to have work happen on a schedule or in reaction to an event, across the other tools a conversation touches.
Running Intercom work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Intercom natively — no MCP server to host, no OAuth plumbing to maintain — and to the ~260 other apps it supports, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Intercom work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a new conversation comes in → check the contact’s plan and history, draft a first reply for approval, and post a summary to the right Slack channel — automatically, the moment it lands.
- Every morning → pull conversations with no reply in 24 hours and send the list to the support lead.
- When a conversation closes as resolved → log the outcome in your spreadsheet or CRM and tag the contact for a follow-up survey.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Intercom connection and everything downstream.
If you just want to interrogate your conversations from a chat, Intercom’s official MCP server is the right tool and it’s free to connect. If you want Intercom to actually do things — on a trigger, on a schedule, across every app a conversation flows through — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Intercom have an official MCP server?
Yes. It’s hosted at https://mcp.intercom.com/mcp, maintained directly by Intercom, and provides 13 tools covering conversations, contacts, companies, and help center articles — most read-only, with the ability to create and update articles.
Is the Intercom MCP server free? Connecting it is free — you’re authorizing an AI client against your existing Intercom account with either OAuth or a bearer token. You still need whatever Intercom plan your workspace runs on, and currently it only supports US-hosted workspaces.
Can the Intercom MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Intercom work across apps, you need a workflow tool like Carly rather than an MCP server.
Can I connect Intercom to AI without coding or hosting a server? Yes. You don’t have to touch MCP at all. Carly connects to Intercom for you and lets you build the automation in plain language — describe what you want to happen and it wires up Intercom and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
