# Apollo.io Sequences (Emailer Campaigns): MCP server status, API access gate and what it does

> Apollo's outbound-sequencing feature - multi-step, multi-channel (email/call/task) cadences that enroll... Official MCP, Enterprise only. Checked 2026-08-24.

*Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).*

*Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.*

---
[Directory](../index.md) /
[Engagement & Outbound](../categories/engagement-outbound.md) /
Apollo.io Sequences (Emailer Campaigns)

# Apollo.io Sequences (Emailer Campaigns)

[Official MCP](../mcp/official.md)
[Enterprise only](../gates/enterprise-only.md)
[Engagement & Outbound](../categories/engagement-outbound.md)
RESEARCHED
Checked 2026-08-24

> **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: [apollo.io](https://apollo.io) · entry id 02-apollo-io-sequences · source 02-engagement-outbound.md line 464

**What it does**
Apollo's outbound-sequencing feature - multi-step, multi-channel (email/call/task) cadences that enroll contacts pulled from Apollo's prospecting database and track send/reply state.

**AI features, separated from automation with an AI label on it**
No sequence-specific AI capability was independently verified beyond standard automation (step sequencing, contact-state tracking to prevent double-sends). Apollo's separate "AI Assistant"/"AI Research" features (documented under its data-enrichment entry) are account-level, not sequence-specific.

**RevOps role**
Execution/engagement module inside Apollo's core platform - same product surface as its prospecting/enrichment tool but a distinct API namespace for enrolling and managing cadences.

**MCP server**

- **Status bucket**: Official MCP

- **Auth**: OAuth (Apollo.io sign-in/authorization flow; no API key required for this MCP)

- **Parsed URLs**: 2 found in the mcp_url field

- **Endpoint probe**: repo or package: install and run locally
- **Docs URL**: [https://github.com/apolloio/apollo-mcp-plugin](https://github.com/apolloio/apollo-mcp-plugin)
- **Probed**: 2026-09-04, HTTP 200

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-08-24. On 2026-09-04 the recorded URL was a reachable repository or package: a server you install and run on your own machine over stdio. Callable after an install, not a remote endpoint.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://github.com/apolloio/apollo-mcp-plugin (hosted server at https://mcp.apollo.io/mcp; listed in the official MCP Registry)

- [https://github.com/apolloio/apollo-mcp-plugin](https://github.com/apolloio/apollo-mcp-plugin)
- [https://mcp.apollo.io/mcp](https://mcp.apollo.io/mcp)

**What this server exposes**

- **Tools named**: 20
- **Strongest evidence**: in a README table
- **Harvested**: 2026-09-27
- **Repo read**: apolloio/apollo-mcp-plugin
- **Whose repo**: first-party
- **Catalogue shape**: a fixed catalogue the vendor publishes

A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.

- **Endpoint** `https://mcp.apollo.io/mcp` evidence: in a README table · calling it reads

- **Need** Where to go evidence: in a README table · calling it reads

- **Path** Purpose evidence: in a README table · calling it reads

- **Skill** What it does evidence: in a README table · calling it reads

- **Symptom** What to check evidence: in a README table · calling it reads

- **Transport** Streamable HTTP evidence: in a README table · calling it reads

- **Version** `0.1.1` evidence: in a README table · calling it reads

- **apollo_analytics_sync_report** Retrieve sales analytics metrics and breakdowns. evidence: in a README table · calling it reads

- **apollo_contacts_create** Create a contact in the Apollo workspace. evidence: in a README table · calling it writes

- **apollo_email_accounts_index** List connected email/sending accounts. evidence: in a README table · calling it reads

- **apollo_emailer_campaigns_add_contact_ids** Add contacts to an outreach sequence. evidence: in a README table · calling it writes

- **apollo_emailer_campaigns_search** Find outreach sequences by name. evidence: in a README table · calling it reads

- **apollo_mixed_companies_search** Search Apollo's organization database by industry, size, location, and keywords. evidence: in a README table · calling it reads

- **apollo_mixed_people_api_search** Search Apollo's people database by title, seniority, location, and company filters. evidence: in a README table · calling it reads

- **apollo_organizations_bulk_enrich** Enrich multiple organizations in one call. evidence: in a README table · calling it reads

- **apollo_organizations_enrich** Enrich a single organization. evidence: in a README table · calling it reads

- **apollo_people_bulk_match** Match and enrich multiple people in one call. evidence: in a README table · calling it reads

- **apollo_people_match** Match and enrich a single person from available identifiers. evidence: in a README table · calling it reads

- **glama.json** Glama MCP directory metadata. evidence: in a README table · calling it reads

- **server.json** Official MCP Registry metadata (name, version, transport, endpoint). evidence: in a README table · calling it reads

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the [tools index](../tools-index.md).

**Command line**

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

**Access gate**

- **Gate bucket**: Enterprise only

- **Can a solo operator reach it**: Not without a contract

api_gate, verbatim from the file:

enterprise-only

**API documentation**

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

**GitHub health**

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

- [https://github.com/apolloio/apollo-mcp-plugin](https://github.com/apolloio/apollo-mcp-plugin)

**On GitHub**

[github.com/apolloio](https://github.com/apolloio) tied to the vendor by rule 1, account website https://www.apollo.io has the vendor's domain, confidence strong

- **Public repositories**: 10, forks excluded, as read on 2026-09-08
- **Mention MCP**: 1 of them
- **Look like CLIs**: 2 of them
- **Latest push**: 2026-08-31

The five most recently pushed, on 2026-09-08:

| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| [apollo-io-cli](https://github.com/apolloio/apollo-io-cli) | CLI | The Official Apollo.io CLI | 53 | 2026-08-31 | v2.1.0 |
| [claude-statusline](https://github.com/apolloio/claude-statusline) | other | | 1 | 2026-08-26 | |
| [homebrew-apollo-io-cli](https://github.com/apolloio/homebrew-apollo-io-cli) | CLI | Homebrew tap for apollo-io-cli | 1 | 2026-08-07 | |
| [apollo-mcp-plugin](https://github.com/apolloio/apollo-mcp-plugin) | MCP server | Connect Claude Code + Cowork to Apollo MCP via this plugin | 20 | 2026-07-20 | v0.1.1 |
| [n8n-nodes-apollo](https://github.com/apolloio/n8n-nodes-apollo) | plugin or integration | Official Apollo.io n8n community node for lead enrichment and organization enrichment | 1 | 2026-07-17 | |

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

**Jobs it can do**

- [Run an email sequence](../jobs/run-email-sequence.md)
- [Place an outbound call](../jobs/place-outbound-call.md)
- [Read outreach performance](../jobs/read-outreach-performance.md)

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

**Sources**

- [https://www.apollo.io/developers](https://www.apollo.io/developers)
- [https://www.apollo.io/pricing](https://www.apollo.io/pricing)
- [https://github.com/apolloio/apollo-mcp-plugin](https://github.com/apolloio/apollo-mcp-plugin)

3 source URLs. Raw sources field, verbatim:

https://www.apollo.io/developers, https://www.apollo.io/pricing, https://github.com/apolloio/apollo-mcp-plugin

**Notes, verbatim from the file**
Included here as its own entry (rather than folded into Apollo's data-enrichment listing) because it has a genuinely distinct API surface: POST /api/v1/emailer_campaigns to create a sequence and POST /api/v1/emailer_campaigns/{id}/add_contact_ids to enroll contacts, separate from the prospecting/enrichment endpoints. The official MCP server explicitly treats "outreach sequence workflows" as a separate capability group from prospecting/enrichment. Apollo's pricing page states API access generally is offered on "Custom" (negotiated/enterprise) plans; sequences are usable in-app on all tiers, but programmatic API access to them is enterprise-gated.

**Provenance**

- **Entry id**: 02-apollo-io-sequences

- **Source file**: 02-engagement-outbound.md

- **Source line**: 464

- **Tier**: RESEARCHED

- **last_checked**: 2026-08-24

- **Data baked**: 2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).