Ext Ops Panel
Open dashboard
Comparison

LinkedIn vs Techmap Job Postings

LinkedIn is an MCP server published by stickerdaniel. Marketplaces we read that list it: 1 (Docker MCP Catalog). Techmap Job Postings is an MCP server published by TechMap. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceLinkedInTechmap Job Postings
Docker MCP Catalog Listed
Version: sha256:c437eb638f80
Forks (GitHub): 670
Stars (GitHub): 3 840
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (npm): 846
Downloads/week (npm): 56
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 Techmap Job Postings
FactLinkedInTechmap Job Postings
Marketplaces that list it11
Stars (GitHub) (differs)3 840 (better)0 (worse)
Forks (GitHub) (differs)670 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (stickerdaniel/linkedin-mcp-server:1.4.0)On your machine (@techmap/mcp-server)
Transportstdiostdio
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/stickerdaniel/linkedin-mcp-servergithub.com/techmap/mcp.techmap.io
Changes in the last 7 days00
First seen2026-10-112026-10-11

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.

Techmap Job Postings

In its own words, on Official MCP Registry:

Search and count job postings from 185 sources in 250 countries (~8M new per month).

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)

Techmap Job Postings As a local MCP server: npm package

Claude Code
claude mcp add --env "TECHMAP_RAPIDAPI_KEY=<YOUR_TECHMAP_RAPIDAPI_KEY>" --transport stdio job-postings -- npx -y @techmap/mcp-server

Requires: TECHMAP_RAPIDAPI_KEY (secret)

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

Tools each declares

The marketplaces of Techmap Job Postings 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 Techmap Job Postings asks for

  • TECHMAP_RAPIDAPI_KEY (secret)

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

What it can do: LinkedIn · What it can do: Techmap Job Postings · 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