Ext Ops Panel
Open dashboard
Comparison

LinkedIn vs careerdocs

LinkedIn is an MCP server published by stickerdaniel. Marketplaces we read that list it: 1 (Docker MCP Catalog). careerdocs is a plugin bundle for AI coding tools published by Oxford Heavy. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
MarketplaceLinkedIncareerdocs
Docker MCP Catalog Listed
Version: sha256:c437eb638f80
Forks (GitHub): 676
Stars (GitHub): 3 876
Not marked · First seen
Not listed
Community marketplace bmcnaboe/careerdocs-plugin Not listed Not seen in the last pass
Version: 0.7.0
Forks (GitHub): 0
Stars (GitHub): 0
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

LinkedIn vs careerdocs
FactLinkedIncareerdocs
Marketplaces that list it11
Stars (GitHub) (differs)3 876 (better)0 (worse)
Forks (GitHub) (differs)676 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (stickerdaniel/linkedin-mcp-server:1.4.0)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle4
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/stickerdaniel/linkedin-mcp-servergithub.com/bmcnaboe/careerdocs-plugin
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14

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

LinkedIn

In its own words, on Docker MCP Catalog:

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.

careerdocs

In its own words, on Community GitHub marketplaces:

Portable resume and cover-letter workflows with one authoritative profile and verified output.

How to run each

LinkedIn As a local MCP server: Docker image

Claude Code
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.0

Requires: LINKEDIN_COOKIE (secret)

careerdocs As a Claude Code plugin

Claude Code
/plugin marketplace add bmcnaboe/careerdocs-plugin
/plugin install careerdocs@careerdocs-plugin

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

Tools each declares

The marketplaces of careerdocs publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of careerdocs publish no settings it asks for, so we do not compare settings.

What it can do: LinkedIn · What it can do: careerdocs · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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