LinkedIn Toolkit runs on your own machine — the client starts it, so there is no endpoint to ping. 142 installs a week from npm. Last commit 17 Sep 2026.
LinkedIn for AI agents from your own Chrome session: search, profiles, lists, outreach queue.
We read the source, 19 h ago · rules 3dff92dd89df
A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.
writeFileSync(resolve(options.csv), toCsv(profiles, PROFILE_COLUMNS), 'utf8');
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
exec(code, namespace) # noqa: S102 — the source is generated from the contract
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add linkedin-toolkit -- npx -y linkedin-toolkit-mcp
{
"mcpServers": {
"linkedin-toolkit": {
"args": [
"-y",
"linkedin-toolkit-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.linkedin-toolkit]
command = "npx"
args = ["-y", "linkedin-toolkit-mcp"]
{
"mcpServers": {
"linkedin-toolkit": {
"args": [
"-y",
"linkedin-toolkit-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"linkedin-toolkit": {
"args": [
"-y",
"linkedin-toolkit-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
LINKEDIN_TOOLKIT_HOME (Directory for the local SQLite mirror and config. Defaults to ~/.linkedin-toolkit.).
The author declared them in the registry entry; get the values from the project itself.
Read LinkedIn profiles, companies, jobs and messages via your own browser session
Drive your real, logged-in Chrome from any AI agent - 40 tools. Needs our Chrome extension too.
LinkedIn Sales Navigator contact and account search from your logged-in browser.
Drive your real, logged-in Chrome/Edge from AI agents over CDP. Faster. Sharper.
Manage local Chrome profiles on Windows: own cookies, sessions and proxy per profile.
Browser control + session recording MCP for AI coding agents (Claude Code, Cursor) — real Chrome.
Bridge a live Chrome browser to your agent: 150 tools for capture, extraction, and observation.
W3C WebMCP toolkit for Chrome 146. Expose any website as a structured MCP server for AI agents.
Answers built from our own checks of this server.