---
ref: tool:intercom/search-conversations
name: Search conversations
company: company:intercom
workflows: [workflow:chat-buyers-to-sales, workflow:feature-requests-to-linear]
access: [mcp, api]
tags: [capability:search-conversations, category:support, has:api, has:mcp]
docs: https://developers.intercom.com/docs/references/rest-api/api.intercom.io/conversations/searchconversations
updated: 2026-09-29
---

# Search conversations

Returns the conversations that match filters such as state, source type, author email, assignee or a word in the message body.

Note: Returns 20 conversations per page by default and at most 150, paged with `starting_after`. A `source.body` filter matches single words, not phrases.

## 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.

```json
{ "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 anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.