Ext Ops Panel
Open dashboard
Comparison

LinkedIn vs abm-dev

LinkedIn is an MCP server published by stickerdaniel. Marketplaces we read that list it: 1 (Docker MCP Catalog). abm-dev is a plugin bundle for AI coding tools published by abm.dev. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
MarketplaceLinkedInabm-dev
Docker MCP Catalog Listed
Version: sha256:c437eb638f80
Forks (GitHub): 674
Stars (GitHub): 3 859
Not marked · First seen
Not listed
Community marketplace abm-dev-git/abm-mcp Not listed Listed
Version: 0.1.0-47ab19d9
Forks (GitHub): 1
Stars (GitHub): 1
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 abm-dev
FactLinkedInabm-dev
Marketplaces that list it11
Stars (GitHub) (differs)3 859 (better)1 (worse)
Forks (GitHub) (differs)674 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (stickerdaniel/linkedin-mcp-server:1.4.0)Remote server (mcp.abm.dev/mcp)
Transport (differs)stdioStreamable HTTP
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 bundle2
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/stickerdaniel/linkedin-mcp-servergithub.com/abm-dev-git/abm-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)no remote endpoint we checkResponded 8 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

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.

abm-dev

In its own words, on Community GitHub marketplaces:

Enrich B2B people & companies with cited multi-source data (verified work emails, LinkedIn, firmographics, AI research), search/source people at target accounts, and write results back to your CRM. Bundles the abm.dev skill and the MCP connector — zero-paste install.

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)

abm-dev As a Claude Code plugin

Claude Code
/plugin marketplace add abm-dev-git/abm-mcp
/plugin install abm-dev@abm-dev

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

Only abm-dev has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of abm-dev publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: LinkedIn · What it can do: abm-dev · 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