v1.4.1: built to sit beside Apollo's own tools

Apollo published MCP v2 on 2026-09-23, a four-tool router in front of the full catalog, and its Claude Code plugin gained a strategy skill. This release re-measures Apollo Operator against the live endpoints and repositions it around one rule: where Apollo now does a step well, the library offers Apollo's way first and picks up where it hands off. Complementary, not parallel. Same 20 skills.

Kept current

• The router is the default. On the same account, v1 lists 85 tools and about 485 KB of schema; v2 exposes the same catalog through four tools and about 6 KB. The same search returns the same 7,829 people on both.
• The catalog grew by 11 tools in eleven days and v2 stayed at four, which is the design doing its job. Record collections, fields, dynamic AI enrichment, data sources, and CSV exports now dispatch through v2 and are in Apollo's docs.
• Reachability re-verified for the agent tools and the master-key path, and the v2 dispatcher calling convention documented with an example.

Positioned beside Apollo's GTM Strategist

Apollo's plugin now ships /apollo:gtm-strategist, which turns a pipeline goal into one recommended play with real reasoning discipline: diagnose before searching, evidence labelled verified or inferred, a small validation cohort, the tool's own approval gates. It runs on the ordinary connector and it is good.

Apollo Operator now offers it where Targeting starts and takes the handoff it describes itself: warmup and deliverability, independent verification, list composition, suppression, per-company caps, the attrition between a sized audience and a sendable list, and reporting past the reply. Where the two overlap, the operator chooses and the library says the option out loud.

Install from any directory: /plugin marketplace add creatop-gtm/apollo-operator, then /plugin install apollo-operator@creatop. Full detail in the CHANGELOG.