# Reply.io ID: 02-reply-io Page: https://gtmmcps.com/tools/02-reply-io JSON: https://gtmmcps.com/data/tools/02-reply-io.json Documentation references: https://gtmmcps.com/docs/02-reply-io/ Category: Engagement & Outbound MCP support: official Testing: RESEARCHED API access: paid Last checked: 2026-09-07 Endpoint check: unreachable; date: 2026-09-04 Multichannel sales engagement platform for email, LinkedIn, call, and SMS outreach with an AI SDR product layered on top. ## MCP links - https://reply.io/mcp/ - https://github.com/reply-team/reply-mcp ## Sources - https://reply.io/mcp/ - https://reply.io/ - https://github.com/reply-team/reply-mcp ## Research notes Vendor states API/webhook access is included across all pricing tiers starting at Standard ($59/mo); some MCP operations consume metered API credits. Site returned HTTP 403 to direct fetch and was retrieved via a read-only proxy - treat pricing figures as slightly less certain than directly-fetched pages. 2026-09-07: GitHub org reply-team, repo reply-mcp; README reads "Reply.io MCP Server - Connect Reply.io to your AI client" and links reply.io and docs.reply.io/reply-mcp (https://github.com/reply-team/reply-mcp). ## Named capabilities Tool names below are reported by sources. Their presence is not a successful call. - reply_add_contact_to_sequence: Enroll up to 100 existing contacts into a sequence; evidence: docs; party: vendor - reply_add_knowledge_base_source: Add a web-page URL source to a knowledge base; evidence: docs; party: vendor - reply_approve_message: Approve one draft and send it immediately; evidence: docs; party: vendor - reply_assign_email_account_to_sequence: Link a mailbox to a sequence; evidence: docs; party: vendor - reply_assign_linkedin_account_to_sequence: Link a LinkedIn account to a sequence; evidence: docs; party: vendor - reply_assign_schedule_to_sequence: Set the sending schedule (business-hours window); evidence: docs; party: vendor - reply_attach_knowledge_base_to_sequence: Attach a knowledge base to an AI SDR sequence; evidence: docs; party: vendor - reply_attach_offer_to_sequence: Attach an offer to an AI SDR sequence; evidence: docs; party: vendor - reply_attach_playbook_to_sequence: Attach a playbook to an AI SDR sequence; evidence: docs; party: vendor - reply_blacklist_contact: Blacklist a contact's email (or whole domain) from outreach; evidence: docs; party: vendor - reply_bulk_approve_messages: Approve and send up to 100 drafts (atomic batch); evidence: docs; party: vendor - reply_change_contact_owner: Reassign up to 100 contacts to another user; evidence: docs; party: vendor - reply_change_inbox_category: Assign or clear a thread's workspace category; evidence: docs; party: vendor - reply_change_status_in_sequence: Set one contact's per-sequence status; evidence: docs; party: vendor - reply_compare_sequence_performance: Side-by-side metrics for up to 25 sequences; evidence: docs; party: vendor - reply_complete_task: Mark a task completed (with optional call resolution); evidence: docs; party: vendor - reply_create_contact: Create a contact (needs a name plus email or LinkedIn URL); evidence: docs; party: vendor - reply_create_knowledge_base: Create a knowledge base; evidence: docs; party: vendor - reply_create_offer: Create an offer Jason can pitch; evidence: docs; party: vendor - reply_create_playbook: Create a playbook (Team or Organization visibility); evidence: docs; party: vendor - reply_create_reengagement_card: Add a reengagement card (with send-after days); evidence: docs; party: vendor - reply_create_reply_handler: Add a reply handler (question type to instructions); evidence: docs; party: vendor - reply_create_task: Create a standalone task (ToDo / Call / Meeting / LinkedIn and others); evidence: docs; party: vendor - reply_delete_knowledge_base_source: Remove a URL source from a knowledge base; evidence: docs; party: vendor - reply_delete_reengagement_card: Remove a reengagement card; evidence: docs; party: vendor - reply_delete_reply_handler: Remove a reply handler; evidence: docs; party: vendor - reply_diagnose: Explain why a sequence isn't sending and how to fix it; evidence: readme; party: first-party - reply_duplicate_playbook: Duplicate a playbook into a new one; evidence: docs; party: vendor - reply_filter_contacts: List contacts by list/sequence membership and/or free-text search; evidence: docs; party: vendor - reply_generate_offer_from_website: Draft offer fields from a company website (does not save); evidence: docs; party: vendor - reply_get_app_map: Catalog of app areas with in-app navigation steps and links; evidence: docs; party: vendor - reply_get_contact_activity: Activity history for one contact (sends, opens, replies, calls); evidence: docs; party: vendor - reply_get_inbox_emails: List inbox threads (email and LinkedIn) with short previews; evidence: docs; party: vendor - reply_get_knowledge_base: Full detail of one knowledge base (instructions, URL sources); evidence: docs; party: vendor - reply_get_knowledge_base_article: Read a full Help Center article by slug; evidence: docs; party: vendor - reply_get_offer: Full offer content (ICP, value props, proof points, CTAs); evidence: docs; party: vendor - reply_get_playbook: Full playbook, including the instruction body; evidence: docs; party: vendor - reply_get_reengagement_card: Full detail of one reengagement card; evidence: docs; party: vendor - reply_get_reply_handler: Full detail of one reply handler; evidence: docs; party: vendor - reply_get_sequence_stats: Email and LinkedIn performance metrics for one sequence; evidence: docs; party: vendor - reply_get_sequence_step_variants: Read a message step's A/B content variants (subject, body); evidence: docs; party: vendor - reply_get_sequence_steps: List a sequence's ordered steps (type, delay, position, variant count); evidence: docs; party: vendor - reply_list_email_accounts: List mailboxes with connection status, daily limits, tags; evidence: docs; party: vendor - reply_list_knowledge_bases: List Jason knowledge bases; evidence: docs; party: vendor - reply_list_linkedin_accounts: List connected LinkedIn accounts with health and tier; evidence: docs; party: vendor - reply_list_my_tasks: List your tasks, filterable by type / status / due window / contact; evidence: docs; party: vendor - reply_list_offers: List Jason offers (id plus name); evidence: docs; party: vendor - reply_list_pending_approvals: The queue of Jason drafts awaiting approval; evidence: docs; party: vendor - reply_list_playbooks: List Jason playbooks (id, name, visibility); evidence: docs; party: vendor - reply_list_reengagement_cards: List reengagement (win-back) cards in a knowledge base; evidence: docs; party: vendor - reply_list_reply_handlers: List reply handlers in a knowledge base; evidence: docs; party: vendor - reply_list_schedules: List sending schedules (timezone, default flag, slot counts); evidence: docs; party: vendor - reply_mark_contacts_as_replied: Mark up to 100 contacts as replied (or clear the flag); evidence: docs; party: vendor - reply_pause_sequence: Pause a sequence; halt in-flight scheduled steps; evidence: docs; party: vendor - reply_regenerate_message: Ask Jason to rewrite a pending draft (optionally with feedback); evidence: docs; party: vendor - reply_reject_message: Reject a draft and remove the contact from the sequence; evidence: docs; party: vendor - reply_report_unsupported_request: Log a capability Reply.io does not have, for the product team; evidence: docs; party: vendor - reply_search_contacts: Look up contacts by exact email or LinkedIn URL; evidence: docs; party: vendor - reply_search_knowledge_base: Search the Reply.io Help Center for how-to articles; evidence: docs; party: vendor - reply_search_lists: Resolve a contact list name to its ListId; evidence: docs; party: vendor - reply_search_sequences: Find sequences by name / status / archive flag; returns per-sequence summary fields; evidence: docs; party: vendor - reply_search_team_members: Resolve a teammate name/email to their UserId; evidence: docs; party: vendor - reply_send_inbox_reply: Send a reply on an existing thread (body only in v1); evidence: docs; party: vendor - reply_set_sequence_reply_mode: Set Jason's Review / Autonomous reply mode; evidence: docs; party: vendor - reply_start_sequence: Start or resume a sequence so it begins sending; evidence: docs; party: vendor - reply_update_contact: Patch fields on an existing contact; evidence: docs; party: vendor - reply_update_knowledge_base: Rename or edit a knowledge base's instructions; evidence: docs; party: vendor - reply_update_offer: Patch an offer; evidence: docs; party: vendor - reply_update_playbook: Patch a playbook; evidence: docs; party: vendor - reply_update_reengagement_card: Patch a reengagement card; evidence: docs; party: vendor - reply_update_reply_handler: Patch a reply handler; evidence: docs; party: vendor ## CLI evidence Status: official - Reported install command: npm install -g reply-cli; source: https://docs.reply.io/cli/overview - Reported install command: npx -y reply-cli; source: https://docs.reply.io/cli/overview Read current vendor documentation before configuring or running commands.