list_conversationsLABSCO SUMMARY
Support history you can question, without exporting it first.
The useful detail is where the filtering happens: keyword and date narrowing go to Intercom's search API, so a week of conversations comes back already reduced instead of being pulled down and sifted. That is also why the conversation range is capped at 7 days — the tool is built for reviewing a window, not for bulk export. Searching by email content rather than only by contact record is what makes it work on the people who wrote in once and were never created as a contact.
What it is
A read client for Intercom support data. Four tools cover the two questions a support review starts from — what happened in this window, and what happened with this customer — with filtering pushed into Intercom's search API rather than applied after everything is fetched.
What you get
- Conversations across a date range, narrowed by a keyword to include and a keyword to exclude in the same call; the range must not exceed 7 days (list_conversations).
- Every conversation belonging to one customer, addressed by email or Intercom ID, optionally bounded by dates and filtered by a list of keywords (search_conversations_by_customer).
- Conversations found by email content even when no contact record exists — emails are resolved to contact IDs where they can be, and matched in content where they cannot (search_conversations_by_customer).
- Tickets by state — open, pending or resolved — over an optional date range (search_tickets_by_status).
- Tickets belonging to one customer, again by email or Intercom ID (search_tickets_by_customer).
Requirements
Node.js 18.0.0 or higher and an Intercom account with API access. The token from your Intercom account settings goes in INTERCOM_ACCESS_TOKEN. Installing globally gives you the intercom-mcp command; a Docker image is the other route, exposing ports 3000 and 8080. Dates are written as DD/MM/YYYY.
Setup effort
Build from source — git clone https://github.com/raoulbia-ai/mcp-server-for-intercom.git
USE CASES
01
Finding out what people complained about last week
Take the week's conversations with a keyword to include and one to exclude, rather than reading all of them.
02
Getting the full history with one customer before replying
Search by their email or Intercom ID and read the conversations and tickets side by side.
03
Seeing what is still open
Filter tickets by status over the period you care about.
04
Tracing someone who wrote in but was never created as a contact
The email is matched in conversation content when there is no contact record to resolve it to.
4 tools
Listed in project docs. Your client may show a different list.
search_conversations_by_customersearch_tickets_by_statussearch_tickets_by_customerBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- Node.js 18.0.0 or higher
- INTERCOM_ACCESS_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/raoulbia-ai/mcp-server-for-intercom.git
cd mcp-server-for-intercom
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"intercom-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_SERVER_FOR_INTERCOM>/build/index.js"
],
"env": {
"INTERCOM_ACCESS_TOKEN": "<YOUR_INTERCOM_ACCESS_TOKEN>"
}
}
}
}
