devag7/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.**
**22 tools** · 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.0.0 adds offline retirement preview and native Windows privacy checks to
the 22-tool local server.** Its published archive and destinations
have been independently verified. Read the 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 the upgrade and its
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.
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 published 4.0.0 artifact and all four destinations are
independently verified. Native-client first-use cohorts
and broad live-provider compatibility remain unverified.
See execution progress and the linked evidence.
| Area | Current evidence |
| --- | --- |
| HTTP boundary, checkpoints, write accounting | Offline regression and MCP protocol fixtures |
| Account identity, profile ownership, shared budgets | Production tool fixtures plus independent Node-process contention/crash tests |
| Setup diagnostics and cold saved sessions | Offline platform/path fixtures and production runtime fixtures |
| Packed artifact | Isolated install, version/doctor checks and compiled MCP smoke; no LinkedIn request |
| Profiles, feed, jobs, companies and inbox | Registered tools; repository notes contain historical live claims. Current live availability is unknown. |
| Five write tools | Conservative classifiers and transaction fixtures. No live writes were sent in this implementation. New-thread messaging remains experimental. |
| Official OAuth provider | Not connected to the active MCP runtime |
Local checks and CI configuration are evidence of the cases they exercise,
not a guarantee of current provider compatibility or account safety.
---
🚀 Quick start
Use Node.js 20 or later and Google Chrome. The commands below pin 4.0.0; run
them after npm lists that version. 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.0.0 requires
state paths beneath the actual %USERPROFILE% tree. A custom path outside it
will be refused even when an older version accepted it. See the
migration notes.