[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_114":115},"routes/modules.$creator.$moduleId",{"_14":15,"_16":17,"_18":19,"_20":21},"routes/modules.$creator.$moduleId.endpoints",{"_11":12,"_13":-5},"error","Module not found","tools","module",{"_20":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":26,"_36":37,"_38":-5,"_39":-5,"_40":41,"_42":43,"_44":45,"_46":47,"_48":49,"_50":51,"_52":53,"_54":55,"_56":-5,"_57":49,"_58":59,"_60":61,"_62":63,"_64":65,"_66":67,"_68":49,"_69":70,"_71":72,"_73":74,"_75":76,"_77":78,"_79":-5,"_80":-5,"_81":82,"_83":49,"_84":-5,"_85":86,"_87":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98},"apiUrl","https://odel.app/api","creator","reply-team","moduleId","reply-mcp","@reply-team/reply-mcp","displayName","Reply.io","tagline","Manage sequences, contacts, and outreach statistics on Reply.io's sales engagement platform.","iconKey","https://avatars.githubusercontent.com/u/103640260?v=4","category","remote","status","published","visibility","public","metaDescription","deploymentType","external","workerName","bindingName","mcpConfig","{\"url\":\"https://mcp.reply.io\",\"transport\":\"streamable-http\",\"authType\":\"headers\",\"requiredSecrets\":[\"X_API_KEY\"]}","pricingModel","free","creatorUserId","system:external-import","createdAt",1785473115000,"updatedAt",1788164389000,"sourceRegistry","official-mcp-registry","sourceUrl","https://registry.modelcontextprotocol.io/v0/servers?search=io.github.reply-io%2Freply-mcp","sourceVerified",false,"sourceMissingSince","importedAt","upstreamStars",1,"upstreamUpdatedAt",1785793144000,"detectedTransport","streamable-http","detectedAuthType","oauth","probeStatus","ok","lastProbedAt","githubRepoUrl","https://github.com/reply-team/reply-mcp","githubRepoFullName","reply-team/reply-mcp","releaseId","ext-reply-team-reply-mcp","version","1.0.0","descriptionMarkdown","

Reply.io MCP Server

\n\n

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

\n\n

\n $\"Transport\"$ \n $\"License\"$ \n

\n\n---\n\n## Overview\n\nA 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.\n\nNo local installation required. Free for all Reply.io users.\n\n📖 **Full documentation:** [docs.reply.io/reply-mcp](https://docs.reply.io/reply-mcp)\n\n## Where this fits\n\nReply's agentic toolkit is three pieces. They are complementary, not alternatives:\n\n| | What it is | When you want it |\n|---|---|---|\n| **[reply CLI](https://github.com/reply-team/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. |\n| **Reply MCP** (this repo) | A curated tool catalog over `mcp.reply.io` | Your client speaks MCP and has no shell — desktop apps, hosted assistants. |\n| **[reply-skills](https://github.com/reply-team/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. |\n\nMCP gives your agent tools. Skills give it judgement. Most setups want both; a shell-capable\nagent can do everything through the CLI alone.\n\nThe shortest path that works: install the CLI, `reply auth login`, `reply skills install`, then\ntalk to your agent in plain words. MCP is optional — add it when your client has no shell.\n\n## Connect\n\nReply 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.\n\n**Claude Code**\n\n```bash\nclaude mcp add --transport http reply-mcp https://mcp.reply.io \\\n --header \"Authorization: Bearer usk_...your_key...\"\n```\n\n**Desktop apps (Claude, ChatGPT)**\n\nAdd Reply MCP as a remote / custom connector using the URL `https://mcp.reply.io` and authorize with OAuth.\n\nCreate and scope a key under **Settings → API Key** in your [Reply.io dashboard](https://run.reply.io).\n\n> **Note:** Passing credentials in the URL (for example `?api_key=...`) is **not** supported. Always authenticate with the `Authorization` header or OAuth.\n\n- **Full connection guide** (Codex, `mcp-remote` proxy, OAuth): [docs.reply.io/reply-mcp#connect](https://docs.reply.io/reply-mcp#connect)\n- **Authentication & keys:** [docs.reply.io/reply-mcp#authentication](https://docs.reply.io/reply-mcp#authentication)\n\n## Authentication & scopes\n\nReply MCP authenticates as a single Reply.io user, via one of two methods:\n\n- **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.\n- **OAuth** — authorize directly from the client, no key to copy. OAuth grants the **full tool catalog** (all scopes).\n\nEach 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.\n\nSee the full scope list at [docs.reply.io/api-reference/authentication#scopes](https://docs.reply.io/api-reference/authentication#scopes).\n\n## Tools\n\n71 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*.\n\n### Contacts & lists\n\n| Tool | Purpose |\n|------|---------|\n| `reply_search_contacts` | Look up contacts by exact email or LinkedIn URL |\n| `reply_filter_contacts` | List contacts by list/sequence membership or a name/email/company search |\n| `reply_get_contact_activity` | Get a contact's activity history (emails, LinkedIn, calls, events) |\n| ⚠️ `reply_create_contact` | Create a contact |\n| ⚠️ `reply_update_contact` | Patch fields on an existing contact |\n| ⚠️ `reply_change_contact_owner` | Reassign contacts to another team member |\n| ⚠️ `reply_mark_contacts_as_replied` | Flag/unflag contacts as replied (stops automated outreach) |\n| ⚠️ `reply_blacklist_contact` | Blacklist a contact's email or whole domain |\n| `reply_search_lists` | Resolve contact lists to their numeric IDs by name |\n\n### Sequences\n\n| Tool | Purpose |\n|------|---------|\n| `reply_search_sequences` | Find sequences by name, status, or archive state |\n| `reply_list_schedules` | List sending schedules (business-hours windows) |\n| `reply_get_sequence_steps` | Get a sequence's ordered steps (type, delay, variant count) |\n| `reply_get_sequence_step_variants` | Get a step's A/B content variants |\n| ⚠️ `reply_change_status_in_sequence` | Set a contact's status within a sequence |\n| ⚠️ `reply_add_contact_to_sequence` | Enroll contacts into a sequence |\n| ⚠️ `reply_start_sequence` | Start or resume a sequence |\n| ⚠️ `reply_pause_sequence` | Pause a sequence |\n| ⚠️ `reply_assign_email_account_to_sequence` | Attach an email account (mailbox) to a sequence |\n| ⚠️ `reply_assign_linkedin_account_to_sequence` | Attach a LinkedIn account to a sequence |\n| ⚠️ `reply_assign_schedule_to_sequence` | Set a sequence's sending schedule |\n\n### Analytics\n\n| Tool | Purpose |\n|------|---------|\n| `reply_get_sequence_stats` | Email + LinkedIn performance for one sequence, over any date range |\n| `reply_compare_sequence_performance` | Compare performance across multiple sequences side by side |\n\n### Inbox\n\n| Tool | Purpose |\n|------|---------|\n| `reply_get_inbox_emails` | List inbox threads (email + LinkedIn) with short previews |\n| ⚠️ `reply_send_inbox_reply` | Send a reply on an existing inbox thread |\n| ⚠️ `reply_change_inbox_category` | Set or clear a thread's category |\n\n### Tasks\n\n| Tool | Purpose |\n|------|---------|\n| `reply_list_my_tasks` | List your tasks, filtered by type, status, due window, or contact |\n| ⚠️ `reply_create_task` | Create a manual task |\n| ⚠️ `reply_complete_task` | Mark a task as completed |\n\n### Channels & accounts\n\n| Tool | Purpose |\n|------|---------|\n| `reply_list_email_accounts` | List workspace email accounts (status, daily limit, tags) |\n| `reply_list_linkedin_accounts` | List connected LinkedIn accounts (status, health, tier) |\n\n### Team\n\n| Tool | Purpose |\n|------|---------|\n| `reply_search_team_members` | Resolve teammates to their numeric user IDs by name or email |\n\n### Help & workspace\n\n| Tool | Purpose |\n|------|---------|\n| `reply_diagnose` | Explain why a sequence isn't sending and how to fix it |\n| `reply_get_app_map` | Catalog of Reply.io app areas and what the assistant can do in each |\n| `reply_search_knowledge_base` | Search the Reply.io Help Center for how-to answers |\n| `reply_get_knowledge_base_article` | Read a full Help Center article by slug |\n| `reply_report_unsupported_request` | Report a missing capability to the product team |\n\n### AI SDR — Offers\n\n| Tool | Purpose |\n|------|---------|\n| `reply_list_offers` | List AI SDR offers (what Jason can pitch) |\n| `reply_get_offer` | Get one offer in full |\n| ⚠️ `reply_create_offer` | Create a new offer |\n| ⚠️ `reply_update_offer` | Patch an existing offer |\n| ⚠️ `reply_attach_offer_to_sequence` | Attach an offer to an AI SDR sequence |\n| `reply_generate_offer_from_website` | Draft offer content from a company website (review only, saves nothing) |\n\n### AI SDR — Playbooks\n\n| Tool | Purpose |\n|------|---------|\n| `reply_list_playbooks` | List playbooks (named sets of selling instructions) |\n| `reply_get_playbook` | Get one playbook in full |\n| ⚠️ `reply_create_playbook` | Create a new playbook |\n| ⚠️ `reply_update_playbook` | Patch an existing playbook |\n| ⚠️ `reply_duplicate_playbook` | Duplicate a playbook |\n| ⚠️ `reply_attach_playbook_to_sequence` | Attach a playbook to an AI SDR sequence |\n\n### AI SDR — Knowledge bases\n\n| Tool | Purpose |\n|------|---------|\n| `reply_list_knowledge_bases` | List AI SDR knowledge bases |\n| `reply_get_knowledge_base` | Get one knowledge base in full (with URL sources) |\n| ⚠️ `reply_create_knowledge_base` | Create a knowledge base |\n| ⚠️ `reply_update_knowledge_base` | Rename or set a knowledge base's instructions |\n| ⚠️ `reply_add_knowledge_base_source` | Add a web-page URL as a source |\n| ⚠️ `reply_delete_knowledge_base_source` | Remove a URL source |\n| ⚠️ `reply_attach_knowledge_base_to_sequence` | Attach a knowledge base to an AI SDR sequence |\n\n### AI SDR — Reply handlers\n\n| Tool | Purpose |\n|------|---------|\n| `reply_list_reply_handlers` | List reply handlers in a knowledge base |\n| `reply_get_reply_handler` | Get one reply handler in full |\n| ⚠️ `reply_create_reply_handler` | Add a reply handler (how Jason answers a kind of question) |\n| ⚠️ `reply_update_reply_handler` | Patch a reply handler |\n| ⚠️ `reply_delete_reply_handler` | Remove a reply handler |\n\n### AI SDR — Re-engagement cards\n\n| Tool | Purpose |\n|------|---------|\n| `reply_list_reengagement_cards` | List re-engagement cards in a knowledge base |\n| `reply_get_reengagement_card` | Get one re-engagement card in full |\n| ⚠️ `reply_create_reengagement_card` | Add a re-engagement card (how Jason wins back a quiet prospect) |\n| ⚠️ `reply_update_reengagement_card` | Patch a re-engagement card |\n| ⚠️ `reply_delete_reengagement_card` | Remove a re-engagement card |\n\n### AI SDR — Approvals & reply mode\n\n| Tool | Purpose |\n|------|---------|\n| `reply_list_pending_approvals` | List AI SDR draft messages waiting for approval |\n| ⚠️ `reply_approve_message` | Approve a draft and send it immediately |\n| ⚠️ `reply_bulk_approve_messages` | Approve and send multiple drafts at once (atomic) |\n| ⚠️ `reply_regenerate_message` | Ask the AI SDR to rewrite a pending draft |\n| ⚠️ `reply_reject_message` | Reject a draft and remove the contact from that sequence |\n| ⚠️ `reply_set_sequence_reply_mode` | Switch a sequence between Review and Autonomous reply mode |\n\n## Example prompts\n\nOnce connected, you can ask your AI assistant things like:\n\n- \"List my active sequences and how each is performing.\"\n- \"Add john@acme.com to the Demo Follow-up sequence.\"\n- \"Pause the Cold Outreach sequence — we're updating the copy.\"\n- \"Why isn't my Q2 Launch sequence sending?\"\n- \"Show me the AI SDR drafts waiting for approval and approve the good ones.\"\n- \"Compare step-by-step performance for my top two sequences.\"\n- \"Create an offer for our new onboarding service and attach it to the Q3 sequence.\"\n\n## Learn more\n\n- [Reply MCP documentation](https://docs.reply.io/reply-mcp) — capabilities, authentication, and connection guide.\n- [Connecting Reply MCP to your AI model](https://support.reply.io/en/articles/12955018-connecting-reply-mcp-to-your-ai-model) — Help Center walkthrough.\n- [Reply MCP overview](https://reply.io/mcp/)\n- [reply CLI](https://github.com/reply-team/reply-cli) — the same Reply.io surface from a terminal, including every v3 endpoint via `reply api`.\n- [reply-skills](https://github.com/reply-team/reply-skills) — outbound expertise as installable skill packs for your agent.\n- [agents.reply.io](https://agents.reply.io) — how the CLI, MCP and the skills fit together, and which interface to pick.\n\n## License\n\nMIT — see [LICENSE](https://github.com/reply-team/reply-mcp/blob/main/LICENSE).\n","changelogMarkdown","videoKey","requiredSecretsJson","[\"X_API_KEY\"]","publishedAt","priceCents","trialDays",0,"iconType","image","upstream",{"_104":105,"_106":107,"_108":-5,"_109":110,"_111":-5,"_112":113},"requiredSecrets",[103],"tags",[101,102],"assets",[],"stats",{"_99":86,"_100":86},"ratingAvg","reviewCount","common","managed-by-tf","X_API_KEY","topics",[101,102],"license","MIT","language","registryName","io.github.reply-io/reply-mcp","homepage","packages",[],"ENV",{"_116":117,"_118":119,"_120":121},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]