Iby Intercom
Search conversations
Returns the conversations that match filters such as state, source type, author email, assignee or a word in the message body.
Description
Useful for reading a customer's support history before a call. The API returns 20 conversations per page by default and at most 150; page with `starting_after`. A `source.body` filter matches single words, not phrases. Read a full thread with `get_conversation` on the MCP server or `GET /conversations/{conversation_id}` on the API.
search-conversations.md
Search conversations
Returns the conversations that match filters such as state, source type, author email, assignee or a word in the message body.
Useful for reading a customer's support history before a call. The API returns
20 conversations per page by default and at most 150; page with
starting_after. A source.body filter matches single words, not phrases.
Read a full thread with get_conversation on the MCP server or
GET /conversations/{conversation_id} on the API.
Set up
Use the first option your agent supports.
MCP (official, remote)
Add this server to your agent's MCP settings, then sign in when asked.
{ "mcpServers": { "intercom": { "url": "https://mcp.intercom.com/mcp" } } }
Call the MCP tool search_conversations.
Server URL: https://mcp.intercom.com/mcp
API (official)
- Base URL: https://api.intercom.io
- Endpoint:
POST /conversations/search - Auth: send the header
Authorization: Bearer $INTERCOM_API_KEY - Get a key: https://app.intercom.io/a/apps/_/developer-hub/app-packages
- Docs: https://developers.intercom.com/docs/references/rest-api/api.intercom.io
Before doing anything else, make one read-only call to confirm access.
Rules
- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.
Built from these files in the repository
The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.