Reply.io MCP for Claude

Run Reply.io outreach from Claude: sequences, contacts, inbox replies, Jason AI SDR drafts.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Reply.io MCP for Claude connector does

Reply.io MCP for Claude connects a Reply.io sales outreach account to Claude. Anthropic lists 163 tools for building email and LinkedIn sequences, enrolling contacts, replying to inbox threads and approving Jason AI SDR drafts. Sign-in is OAuth, which Reply says grants every tool. Reply's docs say calls that send to prospects run immediately, with no undo.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Reply.io MCP for Claude tools (163)

  • 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
  • reply_connect_integration
  • reply_create_account
  • reply_create_call_resolution
  • reply_create_contact
  • reply_create_contact_custom_field
  • reply_create_knowledge_base
  • reply_create_offer
  • reply_create_playbook
  • reply_create_reengagement_card
  • reply_create_reply_handler
  • reply_create_schedule
  • reply_create_sequence
  • reply_create_sequence_step_variant
  • reply_create_task
  • reply_create_trigger
  • reply_delete_call_resolution
  • reply_delete_contact_custom_field
  • reply_delete_email_account
  • reply_delete_knowledge_base_source
  • reply_delete_reengagement_card
  • reply_delete_reply_handler
  • reply_delete_schedule
  • reply_delete_trigger
  • reply_diagnose
  • reply_disconnect_email_account_warmup
  • reply_disconnect_integration
  • reply_disconnect_meetings_calendar_account
  • reply_duplicate_playbook
  • reply_filter_contacts
  • reply_generate_offer_from_website
  • reply_get_account
  • reply_get_account_settings
  • reply_get_accounts_enrichment_settings
  • reply_get_app_map
  • reply_get_billing_info
  • reply_get_contact_activity
  • reply_get_contact_enrichment_mode
  • reply_get_contact_handling_settings
  • reply_get_email_account
  • reply_get_email_account_warmup_status
  • reply_get_email_notification_settings
  • reply_get_email_validation_settings
  • reply_get_inbox_emails
  • reply_get_inbox_notification_settings
  • reply_get_integration_config
  • reply_get_knowledge_base
  • reply_get_knowledge_base_article
  • reply_get_meetings_general_settings
  • reply_get_offer
  • reply_get_playbook
  • reply_get_public_calendar_link
  • reply_get_reengagement_card
  • reply_get_reply_handler
  • reply_get_schedule
  • reply_get_sequence_accounts
  • reply_get_sequence_calls_settings
  • reply_get_sequence_email_limit
  • reply_get_sequence_general_settings
  • reply_get_sequence_stats
  • reply_get_sequence_step_variants
  • reply_get_sequence_steps
  • reply_get_sequence_tasks_settings
  • reply_get_trigger
  • reply_get_workspace_calls_settings
  • reply_get_workspace_email_settings
  • reply_list_account_notes
  • reply_list_account_stages
  • reply_list_beta_features
  • reply_list_blacklist_domains
  • reply_list_call_resolutions
  • reply_list_cloud_calls_team_access
  • reply_list_contact_custom_fields
  • reply_list_contact_notes
  • reply_list_contact_stages
  • reply_list_email_account_sequences
  • reply_list_email_accounts
  • reply_list_email_accounts_by_domain
  • reply_list_integrations
  • reply_list_knowledge_bases
  • reply_list_my_tasks
  • reply_list_offers
  • reply_list_pending_approvals
  • reply_list_playbooks
  • reply_list_reengagement_cards
  • reply_list_reply_handlers
  • reply_list_schedules
  • reply_list_triggers
  • reply_list_voice_profiles
  • reply_mark_contacts_as_opted_out
  • reply_mark_contacts_as_replied
  • reply_pause_sequence
  • reply_regenerate_message
  • reply_regenerate_optout_message
  • reply_reject_message
  • reply_remove_blacklist_domains
  • reply_report_unsupported_request
  • reply_search_accounts
  • reply_search_contacts
  • reply_search_knowledge_base
  • reply_search_lists
  • reply_search_sequences
  • reply_search_team_members
  • reply_send_inbox_reply
  • reply_set_beta_features_enabled
  • reply_set_default_schedule
  • reply_set_sequence_reply_mode
  • reply_set_trigger_enabled
  • reply_start_sequence
  • reply_unarchive_sequence
  • reply_update_account
  • reply_update_account_settings
  • reply_update_account_stage
  • reply_update_accounts_enrichment_settings
  • reply_update_call_resolution
  • reply_update_cloud_calls_team_access
  • reply_update_contact
  • reply_update_contact_enrichment_mode
  • reply_update_contact_handling_settings
  • reply_update_contact_stage
  • reply_update_email_account_optout_settings
  • reply_update_email_account_safety_settings
  • reply_update_email_account_settings
  • reply_update_email_account_signature
  • reply_update_email_notification_settings
  • reply_update_inbox_notification_settings
  • reply_update_integration_config
  • reply_update_knowledge_base
  • reply_update_offer
  • reply_update_playbook
  • reply_update_reengagement_card
  • reply_update_reply_handler
  • reply_update_schedule
  • reply_update_sequence_accounts
  • reply_update_sequence_calls_settings
  • reply_update_sequence_general_settings
  • reply_update_sequence_tasks_settings
  • reply_update_trigger
  • reply_update_workspace_calls_settings
  • reply_update_workspace_email_settings

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Sends are immediate and irreversible, per Reply. Reply's guide, written for its main endpoint, says a successful call executes at once with no undo. Bulk approval sends up to 100 drafts in one call.
  • Confirmation lives in the client. Reply's docs describe no server-side preview or token; the guard is Claude asking you, as the directory listing describes.
  • No narrower grant on this endpoint. OAuth equals all scopes, per Reply. A scoped API key needs a client that sends custom headers, which the Claude apps do not offer for connectors.
  • We could not read schemas or annotations. The endpoint returned 401 to an anonymous request on 2026-11-17; the tool list here is Anthropic's.
  • Reply's docs describe a sibling endpoint. Its 71-tool reference covers mcp.reply.io, not the claude.mcp.reply.io address Anthropic lists with 163 tools.
  • Inbox replies are plain. Reply's v1 reply tool takes a body only: no Cc, Bcc, attachments or scheduling, and a 32,000-character maximum.
  • Rate limits. Reply documents 120 requests per minute, 3,000 per hour and 150,000 per week, with Retry-After on HTTP 429. Our 401 from the Claude endpoint carried a weekly rate-limit header, consistent with the same budget.
  • Single-user only. Team keys and Organization API keys are not supported.

Frequently asked questions

How does authentication work for Reply.io MCP?

Reply's docs describe two methods: a personal API key sent as a Bearer header, or OAuth for apps that only accept a connector URL, such as the Claude desktop and web apps. Reply states OAuth grants the full tool catalogue, equal to an API key with all scopes, with no per-scope control. Team keys and Organization API keys are not supported.

How do I know which Reply.io MCP tools are safe to call?

Reply annotates every tool as read-only or mutating in its tool list, and marks a high-stakes set to confirm every time. Its agent guide says to confirm before anything that sends to a prospect, starts outreach, enrolls contacts, changes ownership, blacklists, bulk-approves or switches Jason to Autonomous. We could not read the annotations on the Claude endpoint, which requires sign-in.

Is the Jason AI SDR autopilot really callable from Claude?

Yes. Anthropic's directory lists tools to approve, bulk-approve, reject and regenerate Jason drafts, and to manage playbooks, offers, knowledge bases and reply handlers. Reply's docs count 31 Jason tools on its main MCP endpoint. Approving a draft sends it immediately, and rejecting one also removes the contact from the sequence, according to Reply's tool reference.

When should you use Reply.io MCP instead of the REST API?

Use MCP for interactive, natural-language work and day-to-day operations, according to Reply's docs. Use the REST API for bulk imports and updates, background jobs, deep report exports and anything the MCP tool list does not cover. Reply's agent guide describes MCP as the interactive surface and the REST API at version 3 as the exhaustive one.

Sources

Use it in an agent

Put Reply.io MCP for Claude to work.

Connect Reply.io MCP for Claude once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.