It does one thing: it finds conversations. That is usually the hard part — the filters cover date ranges, state, channel and read status, so 'everything unread from email since Monday' is a query rather than an afternoon.
An MCP server over the Intercom conversations API. One tool, `search-conversations`, with filters — and each result carries conversation details, contact information, response and reopen counts, and state and priority.
- Conversations filtered by creation date, with an operator and a UNIX timestamp
- Conversations filtered by last update the same way
- Filtering by source type, such as email or chat
- Filtering by conversation state, and by open and read booleans
- Contact information, response and reopen counts, state and priority attached to every result
An Intercom API key, created in your Intercom workspace's developer settings and passed to the server as an environment variable. Clone, `npm install`, `npm run build`, then point your client at `dist/index.js`. Read access only — there is no way here to reply to a conversation or change its state, so it cannot touch your inbox.