Ext Ops Panel
Open dashboard
Comparison

apollo vs HeyLead — AI agent for LinkedIn outreach

apollo is a plugin bundle for AI coding tools published by apolloio. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). HeyLead — AI agent for LinkedIn outreach is an MCP server published by D4umak. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceapolloHeyLead — AI agent for LinkedIn outreach
Claude Code: claude-plugins-official Listed
Version: 0.1.1
Forks (GitHub): 10
Stars (GitHub): 29
Not marked · First seen
Not listed
Official MCP Registry Listed
Version: 0.1.1
Forks (GitHub): 10
Stars (GitHub): 29
Not marked · First seen
Listed
Version: 0.10.462
Downloads/month (PyPI): 18 565
Downloads/week (PyPI): 3 319
Forks (GitHub): 0
Stars (GitHub): 11
Not marked · First seen
Claude Code: claude-plugins-community Listed
Version: 0.1.1
Forks (GitHub): 10
Stars (GitHub): 29
Not marked · First seen
Not listed

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

apollo vs HeyLead — AI agent for LinkedIn outreach
FactapolloHeyLead — AI agent for LinkedIn outreach
Marketplaces that list it (differs)4 (better)1 (worse)
Stars (GitHub) (differs)29 (better)11 (worse)
Forks (GitHub) (differs)10 (better)0 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)Remote server (mcp.apollo.io/mcp)Remote server (heylead.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)6Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/apolloio/apollo-mcp-plugingithub.com/d4umak/linkedin-outreach-mcp
Changes in the last 7 days (differs)017
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agoResponded 44 h ago, requires a key

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

apollo

In its own words, on Claude Code: claude-plugins-official:

Prospect, enrich leads, load outreach sequences, and query sales analytics with Apollo.io — one-click MCP server integration for Claude Code and Cowork.

HeyLead — AI agent for LinkedIn outreach

In its own words, on Official MCP Registry:

AI agent for LinkedIn outreach: finds the right people, writes in your voice, follows up, replies.

How to run each

apollo As a Claude Code plugin

Claude Code
/plugin install apollo@claude-plugins-official

HeyLead — AI agent for LinkedIn outreach As a remote MCP server

Claude Code
claude mcp add --transport http heylead https://heylead.dev/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: apollo · What it can do: HeyLead — AI agent for LinkedIn outreach · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built