@pipeworx/apollo

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/apollo’s. Install: one-click buttons

Connect to just the @pipeworx/apollo pack

https://gateway.pipeworx.io/apollo/mcp — only @pipeworx/apollo’s own tools, nothing else in the catalog.

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 5

Company and people data from Apollo.io: organization search and enrichment, people search and enrichment, and a company’s current job postings. Bring your own Apollo API key — every call runs on your own Apollo account and its own credit balance.

Tools

  • apollo_search_organizations(...) — search companies by industry, headcount, HQ location, technologies in use, and funding history/size.
  • apollo_enrich_organization(...) — enrich one company by domain, website, or LinkedIn URL: industry, headcount, revenue, funding rounds, technologies.
  • apollo_search_people(...) — search people by job title, seniority, and employer domain/org id. Returns an obfuscated last name and never an email or phone — pair with apollo_enrich_person to resolve a real contact.
  • apollo_enrich_person(...) — enrich one specific person by email, LinkedIn URL, or name+domain/organization: title, seniority, department, employer, and (if your account has unlocked it) a work email.
  • apollo_org_job_postings(...) — a company’s current job postings (title, location, posted/last-seen dates), given an Apollo organization_id.

Auth

BYO only. Every tool requires _apiKey — your own Apollo API key, from the Apollo app under Settings → Integrations → API (see https://docs.apollo.io/docs/create-api-key). Pipeworx holds no Apollo key and never substitutes one: with no _apiKey, every tool refuses before making any network call, and the refusal names the argument and the key page.

A scoped key needs that specific endpoint enabled (Apollo lets you scope a key per endpoint); a master key works for all five. Apollo documents a limit of 600 calls/hour per endpoint.

Credit costs (Apollo’s own, charged to your account)

  • apollo_search_organizations — 1 credit per page (up to 100 results/page).
  • apollo_enrich_organization — 1 credit per organization enriched.
  • apollo_search_people — 0 credits (this endpoint never returns email/phone).
  • apollo_enrich_person — 1 credit if email/demographic data is found, +8 more only for a mobile phone (not requested by this pack), 0 if nothing matches.
  • apollo_org_job_postings — 1 credit per page, up to 10,000 postings total.

Pipeworx never marks these up or resells them — they are Apollo’s own usage, billed by Apollo to your account. Pipeworx’s own per-call charge is separate and unrelated to Apollo’s credit cost.

Data sources

  • Apollo.io — company and contact database (organizations, people, job postings) that your own Apollo account already has access to.

Known gaps and gotchas

  • apollo_search_people never returns an email or phone. Apollo deliberately keeps this endpoint credit-free by never including them — you get a first name, an obfuscated last name, and booleans like has_email. Call apollo_enrich_person on a result to try to resolve a real contact.
  • A matched-but-locked email comes back from Apollo as the literal string email_not_unlocked@<domain>, HTTP 200 — not null, not an error. This pack treats that placeholder as a miss: apollo_enrich_person maps it to email: null, email_locked: true rather than ever returning the placeholder text itself. Unlocking it costs your own Apollo credits/plan tier; this pack cannot change that.
  • No phone-number reveal. Apollo’s reveal_phone_number is asynchronous — it delivers the number later to a webhook_url rather than in the response — which has no honest mapping onto a single stateless tool call. This pack does not implement it; use Apollo’s own dashboard/API directly for that leg.
  • No sequences, no contact/list creation, no email sending. Apollo’s API supports all three; this pack implements none of them by design (D3 in docs/gtm-wave-2026-10-08.md).
  • No platform key, ever. This is a BYOK-only pack by design (D4): Apollo is a person-data vendor, and D4 bars adding a new platform-keyed one. Do not add platformKeyEnv to this pack’s gateway manifest entry.
  • No baked enum data. Apollo’s industry tag ids and 1,500+ technology UIDs are both open-ended lists maintained by Apollo, not enumerated here — they are plain string/string[] fields. Look up exact values in the Apollo UI’s own filters.
  • Also usable as a vendor leg (_apolloKey) in enrich_find_email (@pipeworx/enrich-waterfall), alongside its other email-finder vendors.

Tools

Tools

Regenerated from source · build October 15, 2026