LinkedIn MCP

🔗 LinkedIn MCP

LinkedIn for AI assistants — structured data via a real, stealth browser session

Structured LinkedIn reads for MCP clients — profiles, jobs, companies and inbox data, with guided offline setup and explicit safety limits.

24 tools · 4.4.0 follow-up planning · local browser reads · five explicitly confirmed writes · persisted safety limits and operation journals.

This is an unofficial LinkedIn integration and accounts can be restricted.

Review Account safety and SECURITY.md before use.

---

Guided first run

4.4.0 adds an optional local follow-up queue to the application tracker. Supply an explicit reference time to see overdue, due-now, upcoming, unscheduled and closed records. Nothing is scheduled or sent; your records and CSV stay unchanged. It retains 4.3.0 interview practice, 4.2.0 evidence reuse and resume/cover-letter drafts, 24 tools, reviewed dependency repairs and the SDK input guard. See the release notes and readiness record. The commands below target 4.4.0; check its release availability and destination verification before installing. These instructions do not establish publication, native use or broader live compatibility.

The immutable 4.1.1 archive/tag have newly reported October 26 dependency advisories. Their verified bytes and historical receipts do not establish current security clearance. Source contributors can use a reviewed checkout for offline setup and verification. 4.1.0 introduced local application worksheets and CSV export; neither fills or submits applications.

4.0.0 added offline retirement preview and native Windows privacy checks. Read its breaking Windows upgrade notes before changing an existing installation. This is a local stdio tool; Glama's generic “Deploy Server” or browser-hosting controls are not supported installation instructions. No hosted service is required. 4.0.0 release notes describe those changes and limits. Verified 3.1.0 publication receipts remain available for the preceding release.

Start with the quick start and setup guide. Setup reports local issues, client configuration and exact next steps without contacting LinkedIn. Merge the generated entry into your existing client file. See the synthetic setup demonstration: real published package, disposable fixtures, no login or LinkedIn request.

research_jobs is not included; its job-research brief remains in draft PR #5. The execution plan tracks first use, privacy, future features and measured distribution outcomes. The current completion status separates released features from remaining native, live and distribution gates. The October 21 full-scope audit maps all original requirements and later job-seeker additions to their remaining work. The owner-run private GitHub traffic ledger tracks stars and rolling traffic without user telemetry.

For local preparation, prepare_job_application can reuse a user-supplied evidence library and optionally return draft resume bullets and a cover letter. Only explicitly selected claims are included, with their user-provided lineage; missing evidence stays missing. The server stores no library or draft. See the materials workflow.

This version does not fill or submit job applications, including Easy Apply. Use the job seeker and Claude distribution plan for the application handoff workflow, proposed next features and the separate requirements for listing a connector in Claude. Desktop bundle availability and hashes are tracked separately in the bundle guide and release assets. Historical 4.1.1 bundle identity does not clear its newly reported dependency findings; the builder retains its zero-audit gate. For offline source checks, npm run build:claude-mcpb -- --from-source builds an explicitly unreleased checkout bundle. Those checks do not establish native installation or directory acceptance.

What it does

The server uses Patchright to open a persistent Google Chrome profile and makes Voyager requests from its authenticated page. Results are shaped into JSON for MCP clients. Some discovery tools fall back to page data. Undocumented endpoints, query IDs, browser behavior and response shapes can change.

Useful starting workflows are profile research, job/company research and inbox triage. Alpha writes are disabled by default. When enabled they require a reviewed server-issued preview token and confirm:true, consume conservative attempt budgets, and return a status including unknown when completion cannot be established.

Verification status

3.0.0 introduced breaking safety and client requirements; read the migration guide. Hosted source/package/browser checks cover Node20/22 across Linux, macOS and Windows. Exact core-only candidate/head results are recorded in release readiness. One explicitly consented macOS maintainer health/own-profile read also passed with partial metadata; scope and evidence do not establish fresh-user or broader live compatibility. The exact public 4.1.1 bytes and destinations were independently verified; that historical identity proof does not clear current advisories. Consult the 4.1.2 release evidence for its destination status. Native-client first-use cohorts and broad live-provider compatibility remain unverified. See execution progress and the linked evidence.

Local checks and CI configuration are evidence of the cases they exercise, not a guarantee of current provider compatibility or account safety.

---

🚀 Quick start

Using Claude Code? See Claude Code plugin. Comparing Claude routes (plugin, MCPB, ZIP, JSON)? See choose one Claude installation route.

Use Node.js 20 or later and Google Chrome. The commands below target 4.4.0; check its release availability and verification status before installing. Setup is offline; login and subsequent reads are deliberate account actions. For a stable installation path and Windows commands, see the setup guide. On Windows, 4.1.1 retains the requirement that state paths stay beneath the actual %USERPROFILE% tree. A custom path outside it will be refused even when an older version accepted it. See the migration notes.

1. Diagnose offline:

npm install --prefix "$HOME/.local/share/linkedin-mcp" linkedin-mcp-tools@4.4.0

node "$HOME/.local/share/linkedin-mcp/node_modules/linkedin-mcp-tools/dist/index.js" --setup cursor

Also accepts claude-desktop or vscode. Resolve the reported local issues, then merge the generated entry into your existing client file. Setup performs no login or account request. Use a stable local installation and regenerate its entry after upgrades; the report pins its installed build rather than a temporary path.

2. Log in once (opens a real Chrome window — sign in, solve any captcha/2FA):

node "$HOME/.local/share/linkedin-mcp/node_modules/linkedin-mcp-tools/dist/index.js" --login

Needs Google Chrome installed (or run npx patchright install chrome once). Your session — Cloudflare clearance and all — persists to ~/.linkedin-mcp/profile/.

3. Configure your client. Prefer the generated entry above. For clients accepting mcpServers, this version-pinned example is an alternative:

{

"mcpServers": { "linkedin": { "command": "npx", "args": ["-y", "linkedin-mcp-tools@4.4.0"] } } }

Start with whoami for local status. When you deliberately authorize an account read, try *"Read my own profile once and report its returned status and any partial metadata, then close the session. Do not retry or write."* Stop at a checkpoint. Current provider availability is uncertain; preserve empty, partial and error statuses. First-use results across Claude Desktop, Cursor and VS Code have not yet been measured.

Claude Code plugin

Claude Code users can skip step 3 and install the version-pinned plugin from this repository. From any terminal:

claude plugin marketplace add devag7/linkedin-mcp

claude plugin install linkedin-mcp-source@devag7-linkedin-tools

Inside an interactive claude session the equivalents are /plugin marketplace add devag7/linkedin-mcp and /plugin install linkedin-mcp-source@devag7-linkedin-tools. Start a new Claude Code session afterwards. The plugin launches linkedin-mcp-tools@4.4.0 through npx with writes disabled; account reads still need the one-time login (npx -y linkedin-mcp-tools@4.4.0 --login). Pick one installation: do not also add the JSON entry above or the MCPB. This is a community catalog, not an Anthropic directory listing. Review, removal and limits: packaging/claude-source-plugin.

From source / contributing

git clone https://github.com/devag7/linkedin-mcp.git

cd linkedin-mcp npm ci npm run setup:browser # installs the Chrome patchright drives n