Connector · Business and support
An Intercom teammate in Slack, running on Intercom's MCP server.
Chickpea gives a channel a named AI teammate that holds its own Intercom connection. It signs in with OAuth and calls Intercom's MCP server, so there is no client to configure and no token to paste. Ask it in Slack what is open, who holds a conversation, or what a company wrote in about, and it answers in the thread.
What people ask it.
The teammate is @support, in #billing. Pick a scenario to watch it play.
| Conversation | Who wrote in | Assignee | Open since |
|---|---|---|---|
| 41802 | Northwind | Nobody | Fri Sep 12 |
| 41815 | Dovetail | Priya | Mon Sep 14 |
| 41818 | Harbour Lane | Dana | Tue Sep 15 |
| 41820 | Kestrel | Nobody | Wed Sep 16 |
| 41822 | Northwind | Dana | Wed Sep 16 |
See what the inbox is holding Read only
@support what is open in Intercom right now, and who has each one
@support which conversations have been open since Friday with nobody on them
Reads never need confirmation. The search tool takes a query language of its own, so open conversations are
object_type:conversations state:open, narrowed byadmin_assignee_idorteam_assignee_id. A long answer comes back as a table in the thread.Find the conversation, the person, or the company Read only
@support find the conversation where the customer said the invoice was charged twice
@support what has Northwind written in about this month, and who there wrote it
One search covers conversations and contacts. Companies have their own list and lookup, and a contact comes back with its custom attributes. What the teammate sees is what the Intercom account you signed in with sees, because it acts through that sign-in.
Leave an internal note Applies at once
@support add a note on conversation 41822 that billing confirmed the refund
@support note on the Northwind thread that engineering has a fix in review
An internal note is the server's only write against a conversation, and it applies at once. Intercom says the note is visible to teammates only and that the tool cannot send a customer-visible reply. The note is attributed to the Intercom admin who authorized the connection.
Draft or publish a Help Center article Asks first
@support draft a Help Center article from this thread about duplicate charges
@support publish the refunds article, it has been sitting in draft since Tuesday
A new article defaults to draft, which stays inside Intercom, so that one goes through. Publishing puts it in front of customers, which is a consequential write, so the teammate shows what it would publish and waits. Changing an article that is already live asks the same way.
On a schedule Applies at once
@support every weekday at 9am Eastern, post the open conversations nobody has taken
@support every Friday at 4pm Pacific, list what is still open from this week
A schedule saves on the spot. It needs an explicit time zone, runs under the Intercom connection of the person who asked, and fails with a named reason rather than running if that connection has gone.
Connect it
Five steps, from Admin or from Slack.
You sign in through a page Chickpea serves, never in Slack. The link the teammate posts is good for one action, for one teammate, for 24 hours.
- In Chickpea Admin, open the teammate, then Connections, find Intercom, and choose Connect. Or ask in Slack,
@support connect Intercom, and follow the link it posts. - Check which region hosts your workspace. The preset carries one address, mcp.intercom.com/mcp, which is Intercom's US server. An EU-hosted or Australian workspace cannot use it.
- Choose who uses it. Team is one shared Intercom account that everyone who can use the teammate acts through. Personal means each member signs in as themselves, and Intercom records their actions as them.
- Choose Continue to sign in. The preset sends no scope, so the teammate gets whatever Intercom's consent screen grants. Intercom's server wants to read contacts and companies, read conversations, write conversations so notes can be added, and read and write Help Center articles.
- Chickpea records the tools the server answered with and hands the teammate that list, which can later be narrowed but never widened. Then ask
@support what is open in Intercom, which reads and changes nothing.
A connection belongs to one teammate. Giving a second teammate Intercom means a second sign-in with its own consent, so the teammate in #eng never inherits the support inbox.
There is no built-in Chickpea skill for Intercom, and none is needed. The tools arrive from Intercom's MCP server: Chickpea connects before it saves anything, records what the server answered with, and exposes only those tools. Intercom documents fourteen. Eleven search, list, or fetch conversations, contacts, companies, and Help Center articles. The other three create an article, update one, and add an internal note. Intercom names every tool the server exposes.
Beside Intercom
What the same teammate usually holds too.
Each is its own connection, granted to the teammate alone. All 37 connectors.
Questions people ask
Is there an Intercom MCP server?
Yes. Intercom runs a hosted MCP server at mcp.intercom.com/mcp over streamable HTTP, with OAuth sign-in or a bearer token, and documents setup for Claude Desktop, Claude Code, Claude.ai, OpenAI, Cursor, Windsurf, and VS Code. Chickpea connects to that same server, so a teammate in Slack uses it with none of those clients installed.
How do I set up the Intercom MCP?
For a coding client, follow Intercom's own docs, since each client keeps its own config. For Slack there is nothing to configure. Open the teammate in Chickpea Admin, choose Intercom, choose Continue to sign in, and approve the workspace. Or ask "@support connect Intercom" in the channel and follow the link it posts.
Does it use Intercom's MCP server or the API?
The MCP server. Intercom is a vendor MCP lane: the deployment connects to mcp.intercom.com/mcp over streamable HTTP and signs in with OAuth. There is no Intercom API key anywhere in this connector, and the connection cannot reach any other address.
Does it work for EU or Australian workspaces?
No. The preset carries one address, mcp.intercom.com/mcp, which is Intercom's US server, and its own note says US-hosted workspaces only. Intercom does run a second MCP server for EU-hosted workspaces, and says Australian ones are not supported yet. Reaching the EU server would be a change to the preset in the product, not something a connection can be pointed at.
Can it reply to a customer?
No. Intercom's MCP server has no tool that sends a customer-visible message, and Intercom says as much on the one conversation write it does have. An internal note is visible to teammates only, nothing reaches the customer, and that tool cannot send customer-visible replies. A teammate can read the thread, tell the channel what it says, and leave a note for whoever picks it up. The reply is still typed by a person in Intercom.
Can it assign, close, or snooze a conversation?
No. None of those are among the fourteen tools Intercom documents. The server reads assignment and state, so the teammate can say a conversation is open with nobody on it, or filter by who holds it, but changing either happens in Intercom. One side effect is worth knowing. Intercom says a note on a snoozed conversation assigned to someone else reopens it.
Can it delete conversations?
No. Intercom documents no delete tool on the MCP server, so there is nothing to call. Underneath that sits a gate that does not depend on the tool list. During a Slack turn Chickpea refuses any MCP tool whose name does not start with an unambiguous read verb unless the message you just sent names that action. Thread history, retrieved content, and stored memory cannot authorize a write on their own.
Is this Fin, and is Intercom now called Fin?
No, and no. Fin is Intercom's own AI agent. It answers customers across chat, email, voice, and Slack, Intercom prices it on outcomes rather than seats, and says it averages a 76 percent resolution rate across more than 12,000 customers. Intercom the company still ships Intercom; fin.ai is where it sells Fin. A Chickpea teammate answers your own team in a Slack channel, on infrastructure you run, and only touches Intercom when someone in the channel asks.
Do I still need Intercom's Slack integration?
Probably, and it does a different job. Intercom's native Slack integration makes a Slack channel a customer channel: a message there creates a conversation in the Intercom Inbox, teammate replies go back into the Slack thread, Fin can answer there, and tickets and outbound broadcasts run through it. A Chickpea teammate does none of that. It sits in your own internal channel, holds an Intercom connection, and answers questions about the inbox when asked.
Where does the OAuth token live?
On your deployment, outside the teammate record. It never enters the model's context, the tool arguments the model writes, or Slack. The model picks a connection by id and the credential goes in at the last step on the way out. Disconnect the account and the stored secret is removed, and any schedule that depended on it fails with a named reason instead of running.
Try it
Give a channel an Intercom teammate.
One deploy into your own Cloudflare account, connect Slack, sign in to Intercom, ask. Apache 2.0, no seats, no metering.
Or run it on Node. The setup guide covers both.
Last checked
Facts on this page were checked against the product and Intercom's own pages on September 17, 2026. This page is also available as markdown at /connectors/intercom.md.