← All integrations

Reply.io MCP server

33 operations0 webhooks

AI-powered sales engagement platform for contacts, multichannel sequences, email accounts, and sending schedules.

Try Reply.io with your agent

Connect Reply.io, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Reply.io on my account, then run one read-only example and show me the result.

Runs once, when you ask

Reply.io tools and triggers

Tools are what your agent can do in Reply.io through Corsair's MCP server. Triggers are the Reply.io events a routine can start from.

Contacts

  • Clear StatusWrite

    Clear clearable contact statuses (opt-out, replied, bounced)

    contacts.clearStatus

  • CreateWrite

    Create a new contact in Reply.io

    contacts.create

  • DeleteDestructive

    Delete a contact [DESTRUCTIVE · IRREVERSIBLE]

    contacts.delete

  • GetRead-only

    Get a contact by ID

    contacts.get

  • Get StatusRead-only

    Get a contact's statuses across sequences

    contacts.getStatus

  • ListRead-only

    List contacts with pagination and optional filters

    contacts.list

  • Search By EmailRead-only

    Search contacts by exact email address

    contacts.searchByEmail

  • Set StatusWrite

    Set contacts' in-sequence status in bulk

    contacts.setStatus

  • UpdateWrite

    Update an existing contact

    contacts.update

Email Accounts

  • Connect GmailWrite

    Get the Gmail OAuth connect URL for the user to open

    emailAccounts.connectGmail

  • Connect Office365Write

    Get the Microsoft 365 OAuth connect URL for the user to open

    emailAccounts.connectOffice365

  • DeleteDestructive

    Delete an email account [DESTRUCTIVE · IRREVERSIBLE]

    emailAccounts.delete

Connect Reply.io to Claude, ChatGPT or Cursor

  1. 1

    Connect Reply.io in Corsair

    Add your Reply.io API key once in Corsair. Corsair stores the credential encrypted and makes the Reply.io API calls for your agent, so it never goes into a prompt or a config file. Connect Reply.io

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Reply.io. On a ChatGPT personal plan, connect Reply.io here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Reply.io's read and write operations run right away and its 4 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/replyio, add the Reply.io plugin, and connect with an API key. Then call methods like corsair.replyio.api.contactLists.list() from your app. Corsair keeps each tenant isolated.

Yes. Reply.io requires an API key from your Reply.io account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Reply.io, GitHub, Notion, Stripe, and the rest. Trigger Reply.io from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for ai-powered sales engagement platform for contacts, multichannel sequences, email accounts, and sending schedules. Common builds include sync jobs, admin tooling, and agents that call Reply.io APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Reply.io API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/replyio in the open repo. When Reply.io ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Reply.io data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Reply.io data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Reply.io on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 4 destructive Reply.io operations. You can change a link's mode at hub.corsair.dev/me.