---
ref: tool:front/search-conversations
name: Search conversations
company: company:front
workflows: []
access: [mcp, api]
tags: [capability:research-accounts, category:support, has:api, has:mcp]
docs: https://dev.frontapp.com/reference/search-conversations
updated: 2026-09-27
---

# Search conversations

Returns the conversations that match search text and filters such as sender, contact, tag, inbox, assignee, status or date.

On the API, URL-encode the query: search text plus filters such as `from:`
with an email address, `contact:`, `tag:` or `is:open`. Filters combine with
AND, up to 15 at once, and results come most recent activity first. The endpoint is limited to 40% of the company's rate limit. On
the MCP server, set `scope` to `all_inboxes` to include unassigned
conversations: the default searches only the caller's own.

Over MCP, connect with the client ID and secret of a Front developer app that
has MCP Server access: Front has no Dynamic Client Registration.

## 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": { "front": { "url": "https://mcp.frontapp.com/mcp" } } }
```

Call the MCP tool `search_conversations`.

Server URL: https://mcp.frontapp.com/mcp

### API (official)

- Base URL: https://api2.frontapp.com
- Endpoint: `GET /conversations/search/{query}`
- Auth: send the header `Authorization: Bearer $FRONT_API_KEY`
- Get a key: https://dev.frontapp.com/docs/create-and-revoke-api-tokens
- Docs: https://dev.frontapp.com/reference/introduction

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.