Reply.io

Name: Reply.io
Author: reply-team

by reply-teamversion 1.0.0i★ –iRuns in the cloud

Registry nameio.github.reply-io/reply-mcp

Install

Overview

Description from the maker (original English)

Manage sequences, contacts, and outreach statistics on Reply.io's sales engagement platform.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi0 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other
You need to fill in: X-API-Key

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 0 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: X-API-Key

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http reply https://mcp.reply.io --header 'X-API-Key: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "reply": {
      "url": "https://mcp.reply.io",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "reply": {
      "type": "http",
      "url": "https://mcp.reply.io",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

X-API-Key secret required HTTP header
Reply.io API key from your account settings

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

! Caution
Maker matches the repo
The publisher (reply-io) is not the repo owner (reply-team); someone else may have listed it
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32505 servers in this category
Published to the registry more recently than 17% of the other 32505 servers in this category
Basic checks equal to or better than 32% of the other 32505 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Reply.io safe?

It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: X-API-Key

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, topo^alpin

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

topo^alpin

by topoalpin.app

Avalanche bulletins and mountain weather forecasts for any place in the Alps.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Reply.io MCP Server

Connect Reply.io to your AI client and let it work across your team and workspace.

reply.io · Documentation

Overview

A remote MCP server at mcp.reply.io that lets MCP-compatible AI clients — Claude, ChatGPT, Cursor, Codex, and more — work with your Reply.io CRM and AI SDR. One connection gives an agent a catalog of tools spanning contacts, sequences, inbox, tasks, analytics, and the AI SDR ("Jason"), so it can read and act on Reply data without making direct HTTP requests. The tools run the same logic as the Reply.io API and the in-app AI assistant.

No local installation required. Free for all Reply.io users.

📖 Full documentation: docs.reply.io/reply-mcp

Where this fits

Reply's agentic toolkit is three pieces. They are complementary, not alternatives:

	What it is	When you want it
[reply CLI](https://github.com/reply-team/reply-cli)	`npm i -g reply-cli` — authenticated access to every v3 endpoint via `reply api`, with Reply's own skills in the package (`reply skills install`)	Your agent has a shell. This is the complete surface.
Reply MCP (this repo)	A curated tool catalog over `mcp.reply.io`	Your client speaks MCP and has no shell — desktop apps, hosted assistants.
[Jason](https://github.com/reply-team/jason-ai)	Outbound expertise as markdown skills — what to do, in what order, with what guardrails — and a local runtime that keeps campaign work durable (`jason skills install`)	Your agent knows how to call things but not what to run.

MCP gives your agent tools. Skills give it judgement. Most setups want both; a shell-capable agent can do everything through the CLI alone.

The shortest path that works: install the CLI, reply auth login, reply skills install for the Reply skills, and add Jason's skills (jason skills install) for the judgement, then talk to your agent in plain words. MCP is optional — add it when your client has no shell.

Connect

Reply MCP is a remote server at https://mcp.reply.io. Authenticate with a scoped personal API key (recommended) or OAuth, then add it to your client.

Claude Code

claude mcp add --transport http reply-mcp https://mcp.reply.io \

--header "Authorization: Bearer usk_...your_key..."

Desktop apps (Claude, ChatGPT)

Add Reply MCP as a remote / custom connector using the URL https://mcp.reply.io and authorize with OAuth.

Create and scope a key under Settings → API Key in your Reply.io dashboard.

Note: Passing credentials in the URL (for example ?api_key=...) is not supported. Always authenticate with the Authorization header or OAuth.

Full connection guide (Codex, mcp-remote proxy, OAuth): docs.reply.io/reply-mcp#connect
Authentication & keys: docs.reply.io/reply-mcp#authentication

Authentication & scopes

Reply MCP authenticates as a single Reply.io user, via one of two methods:

Personal API key (recommended) — passed as Authorization: Bearer . A personal key is scoped: you grant it only the permissions your agent needs, and it can call only the tools those permissions cover.
OAuth — authorize directly from the client, no key to copy. OAuth grants the full tool catalog (all scopes).

Each tool requires a single scope such as contacts:read or sequences:operate; a key can call a tool only if it holds that scope. Act-on-behalf keys (Team and Organization keys) are not supported on this single-user connection.

See the full scope list at docs.reply.io/api-reference/authentication#scopes.

Tools

71 tools across your CRM and AI SDR. ⚠️ marks destructive tools (create / update / delete / send / assign) — these require the matching :write or :operate scope and carry a destructiveHint so conforming clients can prompt for confirmation. Call arguments (the JSON input schema) are advertised live via tools/list; the tables below describe what each tool is *for*.

Contacts & lists

Tool	Purpose
`reply_search_contacts`	Look up contacts by exact email or LinkedIn URL
`reply_filter_contacts`	List contacts by list/sequence membership or a name/email/company search
`reply_get_contact_activity`	Get a contact's activity history (emails, LinkedIn, calls, events)
⚠️ `reply_create_contact`	Create a contact
⚠️ `reply_update_contact`	Patch fields on an existing contact
⚠️ `reply_change_contact_owner`	Reassign contacts to another team member
⚠️ `reply_mark_contacts_as_replied`	Flag/unflag contacts as replied (stops automated outreach)
⚠️ `reply_blacklist_contact`	Blacklist a contact's email or whole domain
`reply_search_lists`	Resolve contact lists to their numeric IDs by name

Sequences

Tool	Purpose
`reply_search_sequences`	Find sequences by name, status, or archive state
`reply_list_schedules`	List sending schedules (business-hours windows)
`reply_get_sequence_steps`	Get a sequence's ordered steps (type, delay, variant count)
`reply_get_sequence_step_variants`	Get a step's A/B content variants
⚠️ `reply_change_status_in_sequence`	Set a contact's status within a sequence
⚠️ `reply_add_contact_to_sequence`	Enroll contacts into a sequence
⚠️ `reply_start_sequence`	Start or resume a sequence
⚠️ `reply_pause_sequence`	Pause a sequence
⚠️ `reply_assign_email_account_to_sequence`	Attach an email account (mailbox) to a sequence
⚠️ `reply_assign_linkedin_account_to_sequence`	Attach a LinkedIn account to a sequence
⚠️ `reply_assign_schedule_to_sequence`	Set a sequence's sending schedule

Analytics

Tool	Purpose
`reply_get_sequence_stats`	Email + LinkedIn performance for one sequence, over any date range
`reply_compare_sequence_performance`	Compare performance across multiple sequences side by side

Inbox

Tool	Purpose
`reply_get_inbox_emails`	List inbox threads (email + LinkedIn) with short previews
⚠️ `reply_send_inbox_reply`	Send a reply on an existing inbox thread
⚠️ `reply_change_inbox_category`	Set or clear a thread's category

Tasks

Tool	Purpose
`reply_list_my_tasks`	List your tasks, filtered by type, status, due window, or contact
⚠️ `reply_create_task`	Create a manual task
⚠️ `reply_complete_task`	Mark a task as completed

Channels & accounts

Tool	Purpose
`reply_list_email_accounts`	List workspace email accounts (status, daily limit, tags)
`reply_list_linkedin_accounts`	List connected LinkedIn accounts (status, health, tier)

Team

Tool	Purpose
`reply_search_team_members`	Resolve teammates to their numeric user IDs by name or email

Help & workspace

Tool	Purpose
`reply_diagnose`	Explain why a sequence isn't sending and how to fix it
`reply_get_app_map`	Catalog of Reply.io app areas and what the assistant can do in each
`reply_search_knowledge_base`	Search the Reply.io Help Center for how-to answers
`reply_get_knowledge_base_article`	Read a full Help Center article by slug
`reply_report_unsupported_request`	Report a missing capability to the product team

AI SDR — Offers

Tool	Purpose
`reply_list_offers`	List AI SDR offers (what Jason can pitch)
`reply_get_offer`	Get one offer in full
⚠️ `reply_create_offer`	Create a new offer
⚠️ `reply_update_offer`	Patch an existing offer
⚠️ `reply_attach_offer_to_sequence`	Attach an offer to an AI SDR sequence
`reply_generate_offer_from_website`	Draft offer content from a company website (review only, saves nothing)

AI SDR — Playbooks

Tool	Purpose
`reply_list_playbooks`	List playbooks (named sets of selling instructions)
`reply_get_playbook`	Get one playbook in full
⚠️ `reply_create_playbook`	Create a new playbook
⚠️ `reply_update_playbook`	Patch an existing playbook
⚠️ `reply_duplicate_playbook`	Duplicate a playbook
⚠️ `reply_attach_playbook_to_sequence`	Attach a playbook to an AI SDR sequence

AI SDR — Knowledge bases

Tool	Purpose
`reply_list_knowledge_bases`	List AI SDR knowledge bases
`reply_get_knowledge_base`	Get one knowledge base in full (with URL sources)
⚠️ `reply_create_knowledge_base`	Create a knowledge base
⚠️ `reply_update_knowledge_base`	Rename or set a knowledge base's instructions
⚠️ `reply_add_knowledge_base_source`	Add a web-page URL as a source
⚠️ `reply_delete_knowledge_base_source`	Remove a URL source
⚠️ `reply_attach_knowledge_base_to_sequence`	Attach a knowledge base to an AI SDR sequence

AI SDR — Reply handlers

Tool	Purpose
`reply_list_reply_handlers`	List reply handlers in a knowledge base
`reply_get_reply_handler`	Get one reply handler in full
⚠️ `reply_create_reply_handler`	Add a reply handler (how Jason answers a kind of question)
⚠️ `reply_update_reply_handler`	Patch a reply handler
⚠️ `reply_delete_reply_handler`	Remove a reply handler

AI SDR — Re-engagement cards

Tool	Purpose
`reply_list_reengagement_cards`	List re-engagement cards in a knowledge base
`reply_get_reengagement_card`	Get one re-engagement card in full
⚠️ `reply_create_reengagement_card`	Add a re-engagement card (how Jason wins back a quiet prospect)
⚠️ `reply_update_reengagement_card`	Patch a re-engagement card
⚠️ `reply_delete_reengagement_card`	Remove a re-engagement card

AI SDR — Approvals & reply mode

Tool	Purpose
`reply_list_pending_approvals`	List AI SDR draft messages waiting for approval
⚠️ `reply_approve_message`	Approve a draft and send it immediately
⚠️ `reply_bulk_approve_messages`	Approve and send multiple drafts at once (atomic)
⚠️ `reply_regenerate_message`	Ask the AI SDR to rewrite a pending draft
⚠️ `reply_reject_message`	Reject a draft and remove the contact from that sequence
⚠️ `reply_set_sequence_reply_mode`	Switch a sequence between Review and Autonomous reply mode

Example prompts

Once connected, you can ask your AI assistant things like:

"List my active sequences and how each is performing."
"Add john@acme.com to the Demo Follow-up sequence."
"Pause the Cold Outreach sequence — we're updating the copy."
"Why isn't my Q2 Launch sequence sending?"
"Show me the AI SDR drafts waiting for approval and approve the good ones."
"Compare step-by-step performance for my top two sequences."
"Create an offer for our new onboarding service and attach it to the Q3 sequence."

Learn more

Reply MCP documentation — capabilities, authentication, and connection guide.
Connecting Reply MCP to your AI model — Help Center walkthrough.
Reply MCP overview
reply CLI — the same Reply.io surface from a terminal, including every v3 endpoint via reply api.
[Jason](https://github.com/reply-team/jason

Only the beginning is shown; read the rest in the repo

Reply.io

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

topo^alpin

README from the maker

Overview

Where this fits

Connect

Authentication & scopes

Tools

Contacts & lists

Sequences

Analytics

Inbox

Tasks

Channels & accounts

Team

Help & workspace

AI SDR — Offers

AI SDR — Playbooks

AI SDR — Knowledge bases

AI SDR — Reply handlers

AI SDR — Re-engagement cards

AI SDR — Approvals & reply mode

Example prompts

Learn more