REPLY.IO

MCP办公协作

提供方 reply-team

办公协作 未标注 API Key 社区 / 第三方 ClaudeCursorCodexZed

Reply.io is a sales engagement platform used by thousands of B2B sales teams to automate multichannel outreach — email, LinkedIn, calls, SMS, and WhatsApp. The Reply.io MCP server exposes the platform's core functionality as tools that any MCP-compatible AI model can call directl

一句话选型结论

按资料字段整理

REPLY.IO 属于办公协作类 MCP 服务器,传输方式未标注,API Key,可直接接入 Claude、Cursor、Codex 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类办公协作 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

办公协作
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

sales lead generation sales automation

支持客户端

适用场景

saleslead generationsales automation

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程与消息

查日程、发消息、约会议。

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、Codex,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在办公协作场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
REPLY.IO当前 未标注 未标注 未标注 无 未标注
CowAgent 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Karakeep MCP 未标注 未标注 未标注 无 2026-05-17
agentscope 未标注 stdio · 本地进程 本地部署 有 2026-04-11
note-gen 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Everywhere 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

办公协作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方reply-team上游标注的维护方 reply-team
分类办公协作本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

11.0 KB
来自项目仓库与上游目录的原文,未做删改

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 npm i -g reply-cli — authenticated access to every v3 endpoint via reply api 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.
reply-skills Outbound expertise as markdown skills: what to do, in what order, with what guardrails 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, 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 Codebash 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.
  • reply-skills — outbound expertise as installable skill packs for your agent.
  • agents.reply.io — how the CLI, MCP and the skills fit together, and which interface to pick.

License

MIT — see LICENSE.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
REPLY.IO 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

REPLY.IO 怎么在 Claude、Cursor、Codex 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

REPLY.IO 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

REPLY.IO 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

REPLY.IO 支持哪些客户端?

资料标注支持 Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

REPLY.IO 能提供哪些能力?

资料显示能力标签包括 sales、lead generation、sales automation。具体工具清单以官方文档为准。

REPLY.IO 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。