Reply MCP server

What the model can do

Reply.io sales engagement: contacts (look up by email or LinkedIn, stage, owner, opted out) and the notes on them, sequences with status and health, tasks, and the inbox of email and LinkedIn conversations. Can add a note to a contact, create, update, opt out or delete contacts, start, pause or archive sequences, add contacts to a sequence, move or remove them, send a contact a one-off email, reply in an inbox thread and file it under a category, and create, complete, reassign or delete tasks, when you ask.

Reads

• replyio_list_contactsContacts in Reply: name, email, title, company, pipeline stage, owner, opted out, call and meeting status, when added and last changed.
• replyio_get_contactOne Reply contact by id, with company size, industry, country and the contact's notes field (cut at 500 characters).
• replyio_contact_notesThe notes recorded on a Reply contact's timeline, newest first: text, author and when.
• replyio_list_sequencesReply sequences, newest first: id, name, status (new, active, paused), archived, health (healthy, stalled, degraded, blocked), owner and when created.
• replyio_list_tasksTasks in Reply (yours, and teammates' where your role allows): type, status, contact, assignee, start and due, finished…
• replyio_inbox_threadsReply's inbox, most recently active first: email and LinkedIn conversations with contacts — channel, read or not, subject…
• replyio_inbox_categoriesThe categories Reply's inbox files conversations under (yours and Reply's reserved ones): id, name, reserved and unread count.

Acts, when you ask

These change something in Reply. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• replyio_add_contact_noteAdds a note (up to 512 characters) to a Reply contact's timeline.
• replyio_create_taskCreates a to-do, call or meeting task in Reply for the key's own user, optionally about a contact (required for call and meeting).
• replyio_create_contactAdds one contact to Reply.
• replyio_update_contactChanges fields on one Reply contact; fields left out stay as they are.
• replyio_delete_contactPermanently deletes one Reply contact by id, with their place in any sequence.
• replyio_set_contacts_opted_outOpts up to 100 named Reply contacts out of all outreach (finishing them in every sequence they are in), or clears the flag with opted_out false.
• replyio_start_sequenceStarts a Reply sequence, or resumes a paused one.
• replyio_pause_sequencePauses a running Reply sequence so no further steps are sent; its contacts stay in place and it can be started again.
• replyio_archive_sequenceArchives a Reply sequence (pause it first).
• replyio_add_contacts_to_sequenceEnrols up to 100 named Reply contacts in a sequence.
• replyio_move_contact_to_sequenceEnrols one Reply contact in a sequence, optionally taking them out of their current one (remove_from_existing, default false).
• replyio_remove_contact_from_sequenceTakes one contact out of a Reply sequence: they stop progressing and their progress is lost; the contact and history stay.
• replyio_send_direct_emailSends a one-off email to a Reply contact, outside any sequence, from the account's default mailbox: now, or at send_after (at most 30 days ahead).
• replyio_reply_in_threadSends a reply in an existing Reply inbox conversation (thread id from replyio_inbox_threads) to the contact's stored address…
• replyio_set_thread_categoryFiles a Reply inbox conversation under a category (ids from replyio_inbox_categories), or clears it with category_id null.
• replyio_complete_taskMarks a Reply task done without carrying it out.
• replyio_assign_taskHands one Reply task to a colleague by user id (they must be on your team).
• replyio_delete_taskDeletes one Reply task: an open one is cancelled, a completed one archived, and either way it leaves the task lists.

Connect it

First connect Reply on Dashboard → Connections, then add Memtro to your client once. The Reply tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Reply connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What was the last conversation with Dan Fletcher at Northwind?
• › Which sequences are stalled or blocked right now?
• › What call tasks are due this week, and for which contacts?
• › Reply to Dan's thread that Thursday at two works for the call
• › Pause the Q3 outbound sequence

Questions

Is this an official Reply MCP server?

No. It is Memtro's MCP server with Memtro's Reply connector behind it: the connector reads Reply through its API with the credentials you connect on Dashboard → Connections, and Reply publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Reply?

Only when you ask, and only what it has been granted: add a note to a contact; create a to-do, call or meeting task; create a contact (refused when the email already exists); update a contact's fields; delete a contact; opt contacts out of outreach, or clear it; start or resume a sequence; pause a sequence; archive a sequence; add contacts to a sequence; move a contact to another sequence; remove a contact from a sequence; send a contact a one-off email; reply in an inbox thread; file an inbox thread under a category; complete a task; reassign a task; delete a task. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · CRM and sales

• HubSpot MCP server
• Twenty CRM MCP server
• Salesforce MCP server
• Pipedrive MCP server
• Apollo.io MCP server
• Aircall MCP server