LinkedIn vs career-compass-mcp
LinkedIn is an MCP server published by stickerdaniel. Marketplaces we read that list it: 3 (Docker MCP Catalog, PyPI (MCP servers), Community GitHub marketplaces). career-compass-mcp is an MCP server published by benskamps. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. 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 |  LinkedIn |  career-compass-mcp |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c437eb638f80 Forks (GitHub): 743 Stars (GitHub): 4 179 Not marked · First seen |
Not listed |
| PyPI (MCP servers) | Listed Version: 4.29.0 Downloads/month (PyPI): 68 344 Downloads/week (PyPI): 8 301 Forks (GitHub): 743 Stars (GitHub): 4 179 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 2.16.1 Downloads/month (npm): 2 847 Downloads/week (npm): 536 Forks (GitHub): 0 Stars (GitHub): 6 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 | career-compass-mcp | |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 4 179 (better) | 6 (worse) |
| Forks (GitHub) (differs) | 743 (better) | 0 (worse) |
| Last release (differs) | 2026-11-01 (worse) | 2026-11-08 (better) |
| Where it runs (differs) | On your machine (stickerdaniel/linkedin-mcp-server:1.4.0) | On your machine (career-compass-mcp) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/stickerdaniel/linkedin-mcp-server | github.com/benskamps/career-compass-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
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
This MCP server allows Claude and other AI assistants to access your LinkedIn. Scrape LinkedIn profiles and companies, get your recommended jobs, and perform job searches. Set your li_at LinkedIn cookie to use this server.
career-compass-mcp
AI-native career co-pilot for Claude — Career KB, resume tailoring, job pipeline, interview prep, and offer evaluation via MCP
How to run each
LinkedIn As a local MCP server: Docker image
claude mcp add --env "LINKEDIN_COOKIE=<YOUR_LINKEDIN_COOKIE>" --transport stdio linkedin-mcp-server -- docker run -i --rm -e LINKEDIN_COOKIE stickerdaniel/linkedin-mcp-server:1.4.0Requires: LINKEDIN_COOKIE (secret)
career-compass-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of career-compass-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of career-compass-mcp publish no settings it asks for, so we do not compare settings.
What it can do: LinkedIn · What it can do: career-compass-mcp · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.