LinkedIn Toolkit MCP server

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.

Shortened. The full README is on GitHub.