Apollo.io Sequences (Emailer Campaigns)

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://mcp.apollo.io/mcp

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.

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.

api_gate, verbatim from the file:

enterprise-only

No documentation URL recorded.

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

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

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

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

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.

• Run an email sequence
• Place an outbound call
• Read outreach performance

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.

• https://www.apollo.io/developers
• https://www.apollo.io/pricing
• 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

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.