Outreach vs LinkedIn Campaign Manager
Outreach is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). LinkedIn Campaign Manager is an MCP server published by ZLeventer. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
| Marketplace |  Outreach | |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.0 Forks (GitHub): 1 327 Stars (GitHub): 13 366 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Downloads/month (npm): 102 Downloads/week (npm): 8 Not marked · First seen |
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
| Fact | Outreach | LinkedIn Campaign Manager |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 13 366 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 327 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.outreach.io/mcp) | On your machine (linkedin-campaign-manager-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 2 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cursor/plugins | github.com/zleventer/linkedin-campaign-manager-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 20 h ago, requires a key | no remote endpoint we check |
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
Outreach
Search sequences, prospects, and Kaia meetings.
LinkedIn Campaign Manager
MCP server for LinkedIn Ads — 19 read-only tools for campaigns, performance, and Lead Gen Forms.
How to run each
Outreach
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
LinkedIn Campaign Manager As a local MCP server: npm package
claude mcp add --env "LINKEDIN_CLIENT_ID=<YOUR_LINKEDIN_CLIENT_ID>" --env "LINKEDIN_CLIENT_SECRET=<YOUR_LINKEDIN_CLIENT_SECRET>" --env "LINKEDIN_TOKEN_PATH=<YOUR_LINKEDIN_TOKEN_PATH>" --transport stdio linkedin-campaign-manager-mcp -- npx -y linkedin-campaign-manager-mcpRequires: LINKEDIN_CLIENT_ID (secret), LINKEDIN_CLIENT_SECRET (secret), LINKEDIN_TOKEN_PATH
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Outreach has a remote endpoint we 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
The marketplaces of Outreach publish no settings it asks for, so we do not compare settings.
What it can do: Outreach · What it can do: LinkedIn Campaign Manager · Compare two other plugins
Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.