LinkedIn Toolkit

LinkedIn Toolkit

LinkedIn blocks AI browser agents. This is how agents get in.

Operator, Browser Use, computer-use models and Playwright bots get challenged or banned on LinkedIn: headless fingerprints, datacenter IPs, machine-speed clicks. LinkedIn Toolkit gives any agent a safe, structured API to your own logged-in Chrome session — through the same internal endpoints the LinkedIn page itself calls, at human pace, under hard caps, with a human approval queue. It is also a free replacement for Waalaxy and PhantomBuster if you never touch an agent at all. No headless browser, no proxies, no cloud session, no telemetry, no subscription.

▶ Try it without installing · Install guide · Full-quality MP4

Recorded against the toolkit's own demo mode (lit serve --http --fake). Every tool call is real; everyone in it is invented.

Quick start

One command, then three clicks in Chrome.

npx linkedin-toolkit-mcp setup --client claude-code

That downloads the extension for your version, checks it, unpacks it to ~/.linkedin-toolkit/extension, prints the pairing token, waits for the extension to connect, and writes the MCP config block into your client's own config file — keeping every other server in it and backing the file up first. --client takes claude-desktop, claude-code, cursor, windsurf, vscode, n8n or print; add --dry-run to see what it would do without touching anything.

Then the three steps Chrome does not let any installer do for you:

1. Open chrome://extensions — type it in the address bar; it does not come up in search.
2. Turn on Developer mode, top right.
3. Click Load unpacked and choose the folder setup printed.

Paste the pairing token into the popup → Settings → Local bridge, and check it took:

lit status

Rather do it by hand, or only want the extension and no agent?

Download linkedin-toolkit-extension-v*.zip from the Releases page, unzip it somewhere permanent (Chrome loads it from that folder on every start), then do the three steps above. Run npx linkedin-toolkit-mcp for the pairing token, and copy the config block for your client out of docs/clients.md.

docs/install.md is the same thing with screenshots, written for somebody who has never loaded an unpacked extension.

Mass unfollow — Preview first, then a small number, then the rest — is in docs/install.md. Read the "Connections are followed too" part before you decide the feature is broken: LinkedIn's Following list does not include your connections, who are followed automatically when you connect, so emptying that list to zero leaves a feed still full of posts. Ticking "Also unfollow my connections" scans your followers list instead, which is the only place that state is visible.

Every client's config file, path and shape: docs/clients.md · one page per ecosystem.

Not using MCP? lit serve --http gives you POST /actions/{action} and a generated GET /openapi.json. Examples in seven languages.

[!IMPORTANT]

Nothing sends without you. Copilot mode is the default: every write an agent makes queues

for your approval in the popup. Hard caps live in the extension — 100 invites, 150 messages, 500

profile visits, 1,000 search results a day — and no agent, CLI flag or config file can raise

them. Read the safety page before you turn Autopilot on.

What it does

Works with your agent

Structured errors carry code, message, retryAfter and howToFix, so an agent recovers or explains itself instead of retrying into a wall. There is an llms.txt and an agent quickstart written for an agent to read and self-install.

Browser agents vs LinkedIn Toolkit

The long version, with the actual detection mechanisms: Why browser agents fail on LinkedIn.

Why extensions broke, and why this one is built to be repaired

LinkedIn's web client now serves nearly all of its data through GET /voyager/api/graphql?queryId= .<32-hex hash>&variables=(...), and those hashes change with each web client release (current: 1.13.46474). The old REST Voyager paths that a generation of 2024–2025 extensions hard-coded return 400, 410 or 500 today. That is the mechanism — not a ban wave. This extension calls the same GraphQL queries the page calls, from inside your own tab, and keeps every query ID in one refreshable table with its capture date and client version: docs/voyager-endpoints.md. lit endpoints check reports which are ok, failed or unverified, and lit endpoints doctor names the query id whose hash went stale and the key in the table that holds it, so drift is a maintenance task rather than an architecture change.

Honestly: those IDs will drift, and re-capturing them is the contribution this project most needs. It is a table edit, not a rewrite — open DevTools on LinkedIn, filter the Network tab for voyager/api, and copy the queryId from a request the page makes; the same hashes are also literal strings inside LinkedIn's JS bundles if you would rather grep for them.

Versus the paid tools

Competitor prices are public list prices checked September 2026 and are approximate — they change, vary by currency and billing term, and each vendor's tiers differ. Feature claims are taken from each vendor's public product pages, also checked September 2026, and tiers move. Check their sites before deciding anything. Corrections welcome via PR — if we have a feature wrong, open one and it gets fixed.

Source for the Waalaxy column: its current Chrome extension listing, "Alien Copilot" by Waapi (Montpellier) — v1.1.3, updated August 2026, roughly 2,000 users, 3.0★ from 3 ratings — which describes itself as "your Waalaxy companion, helps you import prospects". On that listing the extension imports prospects into Waalaxy, and the automation runs on Waalaxy's servers using your session. Listing details read September 2026.

Research Pack

Drop in a CSV with any of name, linkedin_url, email, domain, company. Get back a dossier per row, an enriched CSV, and a list — all local.

lit