Reply.io MCP for Claude
Run your Reply.io outreach from Claude: build sequences, manage contacts, approve Jason AI SDR drafts, and track performance.
Add to Claude (opens in new tab)Reply MCP connects your Reply.io account to Claude, so you can run outreach without opening the dashboard. Sign in with your Reply account, and Claude works with the same data you already have access to.
What you can do:
- Build sequences from scratch: create them, add email and LinkedIn steps, add A/B variants, set schedules and sending accounts
- Start, pause, and archive sequences, and figure out why one isn't sending
- Add and update contacts and companies, enroll them in sequences, mark them as replied or opted out
- Pull sequence stats and compare performance across sequences
- Read and reply to inbox threads
- Work with Jason AI SDR: approve, reject, or regenerate drafts, and manage playbooks, offers, and knowledge bases
- Manage mailboxes, warm-up, signatures, sending limits, and domain blacklists
- Set up automation triggers, tasks, call settings, and CRM integrations
Claude checks with you before high-impact actions like archiving a sequence or changing its owner, so nothing big happens without your OK.
Tools
- reply_add_account_note
- reply_add_blacklist_domains
- reply_add_contact_note
- reply_add_contact_to_sequence
- reply_add_knowledge_base_source
- reply_add_sequence_steps
- reply_approve_message
- reply_archive_sequence
- reply_assign_email_account_to_sequence
- reply_assign_email_account_to_sequence_contacts
- reply_assign_schedule_to_sequence
- reply_attach_knowledge_base_to_sequence
- reply_attach_offer_to_sequence
- reply_attach_playbook_to_sequence
- reply_blacklist_contact
- reply_bulk_approve_messages
- reply_bulk_tag_email_accounts
- reply_change_contact_owner
- reply_change_inbox_category
- reply_change_sequence_owner
- reply_change_status_in_sequence
- reply_compare_sequence_performance
- reply_complete_task
- reply_connect_email_account_warmup
Only use connectors from developers you trust. Anthropic does not control which tools developers make available and cannot verify that they will work as intended or that they won’t change.