Every LinkedIn MCP server, and why none of them is LinkedIn's

• Subio Scrape

  No account
  Low exposureActivePre-1.0 — 0.1.0

  Reads public LinkedIn company and person pages, and a company's public posts when LinkedIn serves them signed out. It never logs in, so it puts no account at risk — and cannot see anything behind the login.

  stdio7 toolsNo writes to LinkedIn

• Bright Data MCP (LinkedIn tools)

  Vendor API key
  Low exposureActive

  A general web-access server with five LinkedIn extractors: hand it a profile, company, job, post or people-search URL and it returns structured JSON. It holds no LinkedIn credential, so there is no account to restrict.

  stdio and Streamable HTTP69 toolsNo writes to LinkedIn

• Anysite MCP Server

  Vendor API key
  Low exposureActive

  A hosted, paid server that returns structured LinkedIn data — profiles, people search, companies, posts, jobs, the Ad Library — plus a dozen other sources, with server-side filtering and export. No LinkedIn login goes anywhere near it, and it cannot write to LinkedIn at all.

  stdio and Streamable HTTP15 toolsNo writes to LinkedIn

• Insaight

  Vendor API key
  Low exposureActivePre-1.0 — 0.1.0

  Research and record-keeping for manual outreach: it briefs you on a person or a company, mines a post's comment thread, and keeps a local ledger of what you sent and what replied. It has no send path at all.

  stdio18 toolsNo writes to LinkedIn

• LinkedIn Ads MCP Server

  OAuth 2.0
  Medium exposureStale

  Campaign Manager through LinkedIn's official Marketing API, on an OAuth app you register yourself: reporting over your own ad accounts, and a write half that can change budgets and delete campaigns in a live account with no preview step.

  stdio25 tools10 writes to LinkedIn

• eliasbiondo/linkedin-mcp-server

  Browser session
  Medium exposureStalePre-1.0 — 0.1.0

  Read-only LinkedIn scraping through a browser you sign into yourself: profiles section by section, company pages, job postings, people search. No write path at all, and no commits in six months.

  stdio and Streamable HTTP7 toolsNo writes to LinkedIn

• stickerdaniel/linkedin-mcp-server

  Browser session
  High exposureActive

  Profiles, companies, jobs, the feed, post search and your own inbox, read through a browser you sign into on your own account. Two tools write — a message and a connection request — and only the message tool takes a confirmation flag.

  stdio and Streamable HTTP19 tools2 writes to LinkedIn

• La Growth Machine MCP

  Browser session
  High exposureActive

  The operational half of an outbound platform, driven from a chat window: audiences, campaign drafts, inbox triage and SQL over your own funnel. Most of its tools never touch LinkedIn, and none of them launches a campaign.

  Streamable HTTP41 tools3 writes to LinkedIn

• Linked API MCP

  Browser session
  High exposureActive

  A paid cloud-browser service whose tools cover messaging, connections, search, fetching, posting, engagement and Sales Navigator, plus admin tools that let an agent manage seats and rate limits. The MIT repository alone does nothing without the vendor.

  stdio and Streamable HTTP62 tools15 writes to LinkedIn

• gtm-api/linkedin-mcp

  Browser session
  High exposureActive

  A hosted service whose meta-tools expose more than 160 LinkedIn actions, discovered at runtime, including Sales Navigator and Recruiter messaging. The ones that write reach a real account, behind a server-side preview-then-confirm gate.

  stdio and Streamable HTTP3 meta-tools19 writes to LinkedIn

• LinkedGrow

  Browser session
  High exposureActive

  A self-hostable four-container outbound application whose MCP server is a route on your own instance. Its read tools touch nothing on LinkedIn; its write tools start real invitations, messages and scheduled posts under your name.

  Streamable HTTP26 tools5 writes to LinkedIn

• southleft/linkedin-mcp

  Session cookie
  High exposureStalePre-1.0 — 0.2.0

  It layers credentials rather than picking one: official OAuth for posting and analytics, a browser session for messaging and search, and a paid scraper API for research. The session path is what carries the account risk.

  stdio83 tools23 writes to LinkedIn

• linkedincli

  Session cookie
  High exposureActivePre-1.0 — 0.1.6

  Profile data, the feed, messaging, connections and engagement, on a session taken from your own browser. No rate limiting, no throttle, no dry run and no confirmation step, and the maintainer forbids running it on a server.

  stdio43 tools17 writes to LinkedIn

Claude Desktop

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. Reached through Settings → Developer → Edit Config, and it needs a full restart, not a window reload. The transport is inferred from the presence of a command key, so no type field is required. The official page publishes no Linux path. Logs land in ~/Library/Logs/Claude/mcp.log and mcp-server-SERVERNAME.log, which is the first place to look when a server does not appear.

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/username/Desktop",
        "/Users/username/Downloads"
      ]
    }
  }
}

modelcontextprotocol.io ↗, read 20 September 2026. which Claude surface reads which file.

Claude Code

Project scope is .mcp.json at the repository root; local and user scope live in ~/.claude.json, where the entry nests under projects → your path → mcpServers. The block below is the file the docs show claude mcp add writing at project scope. Claude Code reads an entry with no type as a stdio server, so a command-and-args block from Claude Desktop moves across unchanged and claude mcp add-from-claude-desktop imports one; type is required only when the entry has a url, where the values are http (alias streamable-http), sse and ws, and a url without one is reported as a configuration error. The CLI form is claude mcp add --transport stdio <name> -- <command> for a local server and claude mcp add --transport http <name> <url> for a remote one.

{
  "mcpServers": {
    "shared-server": {
      "type": "http",
      "url": "https://example.com/mcp"
    }
  }
}

code.claude.com ↗, read 20 September 2026. the three Claude surfaces and their scopes.

Cursor

.cursor/mcp.json for one project, ~/.cursor/mcp.json globally. Same mcpServers key as Claude Desktop and no type field, so a Claude Desktop block moves across unchanged. A remote server uses url plus headers in place of command and args.

{
  "mcpServers": {
    "server-name": {
      "command": "npx",
      "args": ["-y", "mcp-server"],
      "env": {
        "API_KEY": "value"
      }
    }
  }
}

cursor.com ↗, read 20 September 2026. the LinkedIn servers that run in Cursor.

VS Code

The key is servers, not mcpServers. Paste a Claude Desktop block into this file and nothing happens and nothing says why. The file also takes an inputs array for prompted secrets, referenced as ${input:api-key}, so a token never has to be written into the config. One further trap: VS Code forwards configured servers to the Agent Host, which does not read .vscode/mcp.json itself — portable configuration goes in a workspace .mcp.json or ~/.copilot/mcp-config.json.

{
  "servers": {
    "memory": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-memory"]
    }
  }
}

code.visualstudio.com ↗, read 20 September 2026.