# What the Reply MCP server can do

> The Reply MCP server lets an AI agent run your Reply.io workspace directly — sequences, contacts, inbox, and the Jason AI SDR — over the Model Context Protocol. Capabilities are grouped by area below; full technical detail lives in the [canonical docs](https://docs.reply.io/mcp/tools).

Connect the [Reply MCP server](/mcp) and your agent can operate the same sales-engagement workflows your team runs by hand — from prospecting to replies to autonomous follow-up. Actions that send or change data ask for confirmation before they run.

### Sequences & multichannel outreach

Discover and inspect email and LinkedIn sequences — their steps, A/B variants, and performance, including side-by-side comparison across campaigns. Launch, pause, and resume outreach; enroll and manage contacts inside a sequence; connect mailboxes, LinkedIn accounts, and sending schedules; and switch Jason between review and autonomous modes.

### Contacts & lists

Find contacts by email or LinkedIn, filter by list, sequence, or free text, and review full activity history. Create and update contacts, mark replies, reassign ownership, and blacklist an address or an entire domain.

### Unified inbox & conversations

Read inbox threads with previews, send replies, and organize conversations by category.

### Jason AI SDR

Run the autonomous AI SDR end to end: review, approve, reject, or regenerate draft messages one at a time or in bulk; build and maintain the knowledge bases and reply handlers that shape Jason's responses; configure offers (ICP, value propositions, CTAs) and playbooks; and set up reengagement to win back dormant contacts.

### Tasks

List, create, and complete follow-up tasks.

### Workspace & accounts

Resolve the building blocks of a workspace — mailboxes and their limits, connected LinkedIn accounts, sending schedules, lists, and team members.

### Help & navigation

Search the Reply Help Center, read articles, and get pointed to the right area of the app.

---

**Full technical reference** (signatures, arguments, limits, error contract): [docs.reply.io](https://docs.reply.io/mcp/tools) · **Live endpoint:** `https://mcp.reply.io/`