Ext Ops Panel
Open dashboard
Comparison

LinkedIn vs gtm-api: LinkedIn MCP Server

LinkedIn is an MCP server published by stickerdaniel. Marketplaces we read that list it: 1 (Docker MCP Catalog). gtm-api: LinkedIn MCP Server is an MCP server published by gtm-api.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplaceLinkedIngtm-api: LinkedIn MCP Server
Docker MCP Catalog Listed
Version: sha256:c437eb638f80
Forks (GitHub): 702
Stars (GitHub): 3 964
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.0
Downloads/month (npm): 464
Downloads/week (npm): 65
Forks (GitHub): 0
Stars (GitHub): 92
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 gtm-api: LinkedIn MCP Server
FactLinkedIngtm-api: LinkedIn MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)3 964 (better)92 (worse)
Forks (GitHub) (differs)702 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (stickerdaniel/linkedin-mcp-server:1.4.0)Remote server (mcp.gtm-api.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 0
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/stickerdaniel/linkedin-mcp-servergithub.com/gtm-api/linkedin-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 41 h ago

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.

gtm-api: LinkedIn MCP Server

In its own words, on Official MCP Registry:

Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own.

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)

gtm-api: LinkedIn MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http linkedin-mcp https://mcp.gtm-api.com/mcp

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

Only gtm-api: LinkedIn MCP Server has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of gtm-api: LinkedIn MCP Server publish no list of tools, so we do not compare tools.

Settings each asks for

Only LinkedIn asks for

  • LINKEDIN_COOKIE (secret)
  • USER_AGENT

Only gtm-api: LinkedIn MCP Server asks for

  • GTM_MCP_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: LinkedIn · What it can do: gtm-api: LinkedIn MCP Server · Compare two other plugins

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

Where the data comes from: how the catalog is built