Reply.io

io.github.reply-io由 GitHub 帳號 reply-io 發布v1.0.0更新於 Oct 25, 2026

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

已驗證Streamable HTTP可網頁執行溝通與協作資料與分析商業與電商

概覽

AI 產生的概覽

Reply.io 的遠端 MCP 伺服器，讓助理讀取並操作銷售外聯資料：聯絡人、序列、收件匣、任務、分析以及 AI SDR。

可以做什麼
搜尋、篩選、建立和更新聯絡人、清單、負責人與黑名單，並查看聯絡人活動紀錄。尋找序列、查看步驟與 A/B 變體、將聯絡人加入序列、啟動或暫停序列，並綁定信箱、LinkedIn 帳號和寄送排程。讀取單一序列的表現，並依日期範圍比較多個序列。列出收件匣對話、寄送回覆並設定對話分類。列出、建立和完成任務，並查找團隊成員及工作區信箱或 LinkedIn 帳號。管理 AI SDR 的 offer、playbook、知識庫、回覆處理器和再互動卡片，並核准、拒絕或重寫待審草稿。診斷序列未寄送的原因，並檢索 Reply.io 說明中心。
適用情境
適合讓助理直接在 Reply.io 銷售外聯工作區內操作而不必直接呼叫 API，例如查看序列表現、加入或改派聯絡人、處理收件匣，或審核 AI SDR 草稿。適用於桌面應用程式和託管助理等沒有 shell 的 MCP 用戶端；README 指出有 shell 的代理可用 CLI 涵蓋同樣的功能。
執行需求
遠端端點 mcp.reply.io，無需本機安裝。需要 Reply.io 帳號（對所有 Reply.io 使用者免費）。透過 OAuth 或受限的個人 API 金鑰驗證，以 Authorization bearer 權杖或 X-API-Key 標頭送出；金鑰在 Reply.io 後台的設定、API Key 中建立。不支援把憑證放在 URL 中。不支援 Team 和 Organization 代理操作金鑰。
安裝前請注意
此連線以單一 Reply.io 使用者身分存取真實的 CRM 和外聯資料。許多工具被標示為破壞性（建立、更新、刪除、寄送、指派），包括寄送收件匣回覆、將聯絡人加入序列、啟動或暫停序列、封鎖聯絡人，以及核准會立即寄出的草稿；這些需要寫入或操作權限，並帶有破壞性提示。OAuth 會授予完整工具目錄，受限 API 金鑰範圍較窄。核准或拒絕 AI SDR 草稿會觸發實際寄送或移除聯絡人。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Reply.io，將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.reply-io%2Freply-mcp/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "reply-io": {
      "type": "http",
      "url": "https://mcp.reply.io/"
    }
  }
}

README

Reply.io MCP Server

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

[Transport] [License]

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 isWhen you want it
reply CLInpm i -g reply-cli — authenticated access to every v3 endpoint via reply apiYour agent has a shell. This is the complete surface.
Reply MCP (this repo)A curated tool catalog over mcp.reply.ioYour client speaks MCP and has no shell — desktop apps, hosted assistants.
reply-skillsOutbound expertise as markdown skills: what to do, in what order, with what guardrailsYour 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 Code

bash
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.

Authentication & scopes

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

  • Personal API key (recommended) — passed as Authorization: Bearer <token>. 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

ToolPurpose
reply_search_contactsLook up contacts by exact email or LinkedIn URL
reply_filter_contactsList contacts by list/sequence membership or a name/email/company search
reply_get_contact_activityGet a contact's activity history (emails, LinkedIn, calls, events)
⚠️ reply_create_contactCreate a contact
⚠️ reply_update_contactPatch fields on an existing contact
⚠️ reply_change_contact_ownerReassign contacts to another team member
⚠️ reply_mark_contacts_as_repliedFlag/unflag contacts as replied (stops automated outreach)
⚠️ reply_blacklist_contactBlacklist a contact's email or whole domain
reply_search_listsResolve contact lists to their numeric IDs by name

Sequences

ToolPurpose
reply_search_sequencesFind sequences by name, status, or archive state
reply_list_schedulesList sending schedules (business-hours windows)
reply_get_sequence_stepsGet a sequence's ordered steps (type, delay, variant count)
reply_get_sequence_step_variantsGet a step's A/B content variants
⚠️ reply_change_status_in_sequenceSet a contact's status within a sequence
⚠️ reply_add_contact_to_sequenceEnroll contacts into a sequence
⚠️ reply_start_sequenceStart or resume a sequence
⚠️ reply_pause_sequencePause a sequence
⚠️ reply_assign_email_account_to_sequenceAttach an email account (mailbox) to a sequence
⚠️ reply_assign_linkedin_account_to_sequenceAttach a LinkedIn account to a sequence
⚠️ reply_assign_schedule_to_sequenceSet a sequence's sending schedule

Analytics

ToolPurpose
reply_get_sequence_statsEmail + LinkedIn performance for one sequence, over any date range
reply_compare_sequence_performanceCompare performance across multiple sequences side by side

Inbox

ToolPurpose
reply_get_inbox_emailsList inbox threads (email + LinkedIn) with short previews
⚠️ reply_send_inbox_replySend a reply on an existing inbox thread
⚠️ reply_change_inbox_categorySet or clear a thread's category

Tasks

ToolPurpose
reply_list_my_tasksList your tasks, filtered by type, status, due window, or contact
⚠️ reply_create_taskCreate a manual task
⚠️ reply_complete_taskMark a task as completed

Channels & accounts

ToolPurpose
reply_list_email_accountsList workspace email accounts (status, daily limit, tags)
reply_list_linkedin_accountsList connected LinkedIn accounts (status, health, tier)

Team

ToolPurpose
reply_search_team_membersResolve teammates to their numeric user IDs by name or email

Help & workspace

ToolPurpose
reply_diagnoseExplain why a sequence isn't sending and how to fix it
reply_get_app_mapCatalog of Reply.io app areas and what the assistant can do in each
reply_search_knowledge_baseSearch the Reply.io Help Center for how-to answers
reply_get_knowledge_base_articleRead a full Help Center article by slug
reply_report_unsupported_requestReport a missing capability to the product team

AI SDR — Offers

ToolPurpose
reply_list_offersList AI SDR offers (what Jason can pitch)
reply_get_offerGet one offer in full
⚠️ reply_create_offerCreate a new offer
⚠️ reply_update_offerPatch an existing offer
⚠️ reply_attach_offer_to_sequenceAttach an offer to an AI SDR sequence
reply_generate_offer_from_websiteDraft offer content from a company website (review only, saves nothing)

AI SDR — Playbooks

ToolPurpose
reply_list_playbooksList playbooks (named sets of selling instructions)
reply_get_playbookGet one playbook in full
⚠️ reply_create_playbookCreate a new playbook
⚠️ reply_update_playbookPatch an existing playbook
⚠️ reply_duplicate_playbookDuplicate a playbook
⚠️ reply_attach_playbook_to_sequenceAttach a playbook to an AI SDR sequence

AI SDR — Knowledge bases

ToolPurpose
reply_list_knowledge_basesList AI SDR knowledge bases
reply_get_knowledge_baseGet one knowledge base in full (with URL sources)
⚠️ reply_create_knowledge_baseCreate a knowledge base
⚠️ reply_update_knowledge_baseRename or set a knowledge base's instructions
⚠️ reply_add_knowledge_base_sourceAdd a web-page URL as a source
⚠️ reply_delete_knowledge_base_sourceRemove a URL source
⚠️ reply_attach_knowledge_base_to_sequenceAttach a knowledge base to an AI SDR sequence

AI SDR — Reply handlers

ToolPurpose
reply_list_reply_handlersList reply handlers in a knowledge base
reply_get_reply_handlerGet one reply handler in full
⚠️ reply_create_reply_handlerAdd a reply handler (how Jason answers a kind of question)
⚠️ reply_update_reply_handlerPatch a reply handler
⚠️ reply_delete_reply_handlerRemove a reply handler

AI SDR — Re-engagement cards

ToolPurpose
reply_list_reengagement_cardsList re-engagement cards in a knowledge base
reply_get_reengagement_cardGet one re-engagement card in full
⚠️ reply_create_reengagement_cardAdd a re-engagement card (how Jason wins back a quiet prospect)
⚠️ reply_update_reengagement_cardPatch a re-engagement card
⚠️ reply_delete_reengagement_cardRemove a re-engagement card

AI SDR — Approvals & reply mode

ToolPurpose
reply_list_pending_approvalsList AI SDR draft messages waiting for approval
⚠️ reply_approve_messageApprove a draft and send it immediately
⚠️ reply_bulk_approve_messagesApprove and send multiple drafts at once (atomic)
⚠️ reply_regenerate_messageAsk the AI SDR to rewrite a pending draft
⚠️ reply_reject_messageReject a draft and remove the contact from that sequence
⚠️ reply_set_sequence_reply_modeSwitch 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 [email protected] 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

License

MIT — see LICENSE.

來源：README.md，提交 a9779ed

工具

0
該伺服器需要登入，因此 SourceWeft 無法在沒有帳號的情況下讀取其工具，也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.0.0最新Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分