# Reply.io (Jason AI) ID: 04-reply-io Page: https://gtmmcps.com/tools/04-reply-io JSON: https://gtmmcps.com/data/tools/04-reply-io.json Documentation references: https://gtmmcps.com/docs/04-reply-io/ Category: AI SDRs MCP support: official Testing: RESEARCHED API access: paid Last checked: 2026-09-07 Endpoint check: unreachable; date: 2026-09-04 A multichannel sales engagement platform whose AI layer ("Jason AI," per widely reported branding) generates outreach emails/follow-ups and automates sequencing across email, calls, and tasks. ## MCP links - https://reply.io/mcp/ - https://support.reply.io/en/articles/12955018-connecting-reply-mcp-to-your-ai-model - https://github.com/reply-team/reply-mcp ## Sources - https://www.producthunt.com/products/reply-io - https://reply.io/pricing/ - https://reply.io/llms.txt - https://reply.io/mcp/ - https://support.reply.io/en/articles/12955018-connecting-reply-mcp-to-your-ai-model - https://github.com/reply-team/reply-mcp ## Research notes Sourcing gap flagged honestly: reply.io's own marketing pages (including /jason-ai/) returned HTTP 403 to every automated fetch attempt this pass, so this entry leans on a secondary source. Re-verify directly before bench-testing. [api_gate 2026-08-25] Reclassified unknown -> paid from the vendor's own page (https://reply.io/pricing/): API is listed across all four published tiers starting at Starter from $59/mo, and the pricing FAQ says the 14-day trial includes API and all integrations. 2026-09-02: mcp_status none-found -> official. reply.io answers to a browser user agent (the 403s above were to a bare fetcher): https://reply.io/llms.txt lists "Reply MCP" at https://reply.io/mcp/, that page states "Setup takes 5 minutes and just requires copying your API key" and names tools including reply_list_sequences, reply_add_contact_to_sequence, reply_start_sequence, reply_pause_sequence, reply_connect_crm and reply_connect_email_account, and the help article (modified 2026-07-10) documents the per-account MCP Connection URL with API key or OAuth and walks through n8n, Make and Claude connectors. No fixed public endpoint is published; the URL is issued inside the account. Plan requirement not stated on either page. 2026-09-07: Same first-party repo as the Reply.io entry: GitHub org reply-team, README "Reply.io MCP Server", server.json manifest linking 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_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_bulk_approve_messages: Approve and send up to 100 drafts (atomic batch); evidence: docs; party: vendor - reply_compare_sequence_performance: Compare performance across multiple sequences side by side; evidence: readme; party: first-party - 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_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 or a name/email/company search; evidence: readme; party: first-party - 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 Reply.io app areas and what the assistant can do in each; evidence: readme; party: first-party - reply_get_contact_activity: Get a contact's activity history (emails, LinkedIn, calls, events); evidence: readme; party: first-party - reply_get_inbox_emails: List inbox threads (email + LinkedIn) with short previews; evidence: readme; party: first-party - 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: readme; party: first-party - 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 + LinkedIn performance for one sequence, over any date range; evidence: readme; party: first-party - reply_get_sequence_step_variants: Get a step's A/B content variants; evidence: readme; party: first-party - reply_get_sequence_steps: Get a sequence's ordered steps (type, delay, variant count); evidence: readme; party: first-party - reply_list_email_accounts: List workspace email accounts (status, daily limit, tags); evidence: readme; party: first-party - reply_list_knowledge_bases: List Jason knowledge bases; evidence: docs; party: vendor - reply_list_linkedin_accounts: List connected LinkedIn accounts (status, health, tier); evidence: readme; party: first-party - reply_list_my_tasks: List your tasks, filtered by type, status, due window, or contact; evidence: readme; party: first-party - 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 (business-hours windows); evidence: readme; party: first-party - 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: Report a missing capability to the product team; evidence: readme; party: first-party - reply_search_contacts: Look up contacts by exact email or LinkedIn URL; evidence: readme; party: first-party - reply_search_knowledge_base: Search the Reply.io Help Center for how-to answers; evidence: readme; party: first-party - reply_search_lists: Resolve contact lists to their numeric IDs by name; evidence: readme; party: first-party - reply_search_sequences: Find sequences by name, status, or archive state; evidence: readme; party: first-party - reply_search_team_members: Resolve teammates to their numeric user IDs by name or email; evidence: readme; party: first-party - reply_set_sequence_reply_mode: Set Jason's Review / Autonomous reply mode; 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.