Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Reply.io (BYOK) icon

Reply.io (BYOK)

Read your Reply.io sales engagement sequences, contacts, tasks, inbox threads, email accounts and team users with BYOK

Unify Dynamics LLC

Tools12read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderReply.iounofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Reply.io user is my API key for?
Tools called
whoami
Who is on my Reply.io team?
Tools called
list_team_users
Which Reply.io sequences are active?
Tools called
list_sequences
Show Reply.io sequence 1234
Tools called
get_sequence
Who is enrolled in Reply.io sequence 1234 and has replied?
Tools called
list_sequence_contacts
Find the Reply.io contact jane@example.com
Tools called
list_contacts

About

Reply.io (BYOK) lets an AI assistant read your own Reply.io data through the Reply.io API with a key you supply (Reply API key (needs read scopes such as contacts:read and sequences:read)). Read-only: 12 tools (whoami, list_team_users, list_sequences, get_sequence, list_sequence_contacts, list_contacts, list_contact_lists, list_contact_accounts, list_tasks, list_inbox_threads, list_email_accounts, list_sequence_folders). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.reply.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Reply.io. Reply.io and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Reply.io API (api.reply.io) with a BYOK key; documentation: https://docs.reply.io/api-reference/introduction. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

12 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data12 tools
  • WhoamiShow the Reply user and team the key belongs to.
  • List team usersList the users of your Reply team with name, email and role.
  • List sequencesList Reply sequences with owner, status (new, active, paused), health and creation time.
  • Get sequenceGet one Reply sequence: status, health, schedule, connected email accounts and sending settings.
  • List sequence contactsList the contacts enrolled in a Reply sequence with their status in the sequence, reply and bounce flags and current step.
  • List contactsList Reply contacts, or look one up by exact email or LinkedIn URL, with company, title, location and stage.
  • List contact listsList Reply contact lists with name and sharing flag.
  • List contact accountsList Reply accounts (companies) with domain, industry, size, country, stage and activity dates.
  • List tasksList Reply tasks (to-dos, calls, meetings, LinkedIn and manual email steps) with type, status, assignee and due date.
  • List inbox threadsList Reply inbox threads with subject, preview, contact, sequence, category and last activity.
  • List email accountsList the email accounts connected to Reply with sender name, type, daily limit and connection status.
  • List sequence foldersList Reply sequence folders (id and name).

Information

PublisherUnify Dynamics LLC
CategoryWork & productivity
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-replyio.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

More like this

More in Other

Affinity (BYOK)

Read the people, companies, opportunities, lists, list entries and notes in your Affinity relationship CRM with your own API key (API v2)

Live · MCP + REST7 tools

TimeCamp (BYOK)

Read your TimeCamp time entries, projects and tasks, users, groups, running timers and tag lists with your own API token

Live · MCP + REST7 tools

Nusii (BYOK)

Read your Nusii proposals, clients, templates, users and proposal activity such as sends and views with your own API key

Live · MCP + REST8 tools

Tempo (BYOK)

Read Tempo timesheet worklogs, resource planner allocations, teams, accounts, customers, projects and roles for Jira with your own Tempo API token

Live · MCP + REST10 tools

Mixmax (BYOK)

Read your Mixmax sequences and their recipients, email templates, live feed tracking, meeting types and drafts with your own API token

Live · MCP + REST9 tools

Teamgate (BYOK)

Read the leads, people, companies, deals, pipelines, activities and products in your Teamgate CRM with your own application key and user auth token

Live · MCP + REST10 tools

Get Reply.io (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Reply.io Reply API key (needs read scopes such as contacts:read and sequences:read). Create one at https://docs.reply.io/api-reference/introduction, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Reply.io. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Reply.io.