
LinkedIn MCP Server
io.github.prakharagarwal-devPublished by GitHub account prakharagarwal-devv0.16.0Updated Oct 24, 2026
Find LinkedIn jobs and people, research companies, manage network, posts, and messages with MCP.
Overview
An unofficial local MCP server that drives LinkedIn's web UI through a signed-in browser, letting an assistant search jobs, people, companies and posts, and act
- What you can do
- Search and read jobs, including filters, full descriptions and hiring teams. Search people and companies and read profiles, experience, education and company details. Search posts and read content, comments and reactions. Publish posts, comment and react. List and search connections, and list, send, accept or ignore invitations. Search and read conversations, and send or reply to messages.
- When to use it
- Useful when you want an assistant to research LinkedIn jobs, candidates, companies or discussions, or to handle routine network and messaging tasks through your own signed-in account instead of manual browsing.
- Requirements
- Runs locally as a stdio process, launched with uvx from the linkedin-mcp-local package (Python, with Playwright browser requirements). A dedicated browser window opens for you to sign in to LinkedIn and complete any verification; the session is saved in a local browser profile.
Installation
In SourceWeft
- Open LinkedIn MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
LinkedIn MCP Server
[CI] [CodeQL] [PyPI] [Python 3.12–3.14] [License: Apache-2.0] [MCP Registry] [Glama] [OpenSSF Scorecard] [PyPI provenance] [Container provenance and SBOM]
Disclaimer: LinkedIn is a registered trademark of LinkedIn Corporation and its affiliates. LinkedIn MCP Server is an independent, unofficial project and is not affiliated with, endorsed by, sponsored by, or associated with LinkedIn Corporation or its affiliates.
A LinkedIn MCP server to find jobs, search people, research companies, manage your network, publish and engage with posts, and read or send messages.
⚡ Quickstart
1. Connect Claude Code
2. Sign in to LinkedIn
Restart Claude Code. A dedicated browser window opens automatically—sign in to LinkedIn and complete any required verification.
[!NOTE] Your session is saved locally and reused automatically.
Supported platforms
The server runs natively on Windows, macOS, and Linux. CI executes the complete offline suite on Windows, macOS, Linux x86-64, and Linux ARM64. Browser and OS version requirements follow the official Playwright Python system requirements.
3. Try your first request
🛠️ Tools
[!TIP] Verified means the tool passed an end-to-end live compatibility test against LinkedIn's visible web UI on the date shown.
NOT CHECKED tools remain covered by the offline simulator on every pull request.
See the capability matrix for exact filters, supported formats, inputs, outputs, limits, and unsupported features.
📦 Installation
Claude Code
Check it with claude mcp list. See the
Claude Code MCP documentation.
Claude Desktop
Download the .mcpb file, then open Settings → Extensions → Advanced
settings → Install Extension.
See Claude Desktop's extension documentation.
Codex and ChatGPT Desktop
Check it with codex mcp list. Codex CLI, the Codex IDE extension, and ChatGPT
Desktop share this local configuration. Restart the client after adding it. See
the Codex MCP documentation.
VS Code and GitHub Copilot
[Install in VS Code] [Install in VS Code Insiders]
Or add this to .vscode/mcp.json:
See the VS Code MCP documentation.
Cursor
For manual setup, open Cursor Settings → MCP →
Add new MCP server, set the command to uvx, and set the arguments to
--from linkedin-mcp-local linkedin-mcp serve --transport stdio.
See the Cursor MCP documentation.
Gemini CLI
In ~/.gemini/settings.json, add a local server named linkedin-mcp under
mcpServers with command uvx and arguments
--from linkedin-mcp-local linkedin-mcp serve --transport stdio, then run
gemini mcp list.
See the Gemini CLI MCP documentation.
Windsurf
Open Settings → AI → Manage MCP Servers, or add a local server named
linkedin-mcp to ~/.codeium/windsurf/mcp_config.json with command uvx and
arguments --from linkedin-mcp-local linkedin-mcp serve --transport stdio.
See the Windsurf MCP documentation.
Cline
Open MCP Servers → Configure, then add a local server named linkedin-mcp
with command uvx and arguments
--from linkedin-mcp-local linkedin-mcp serve --transport stdio.
See the Cline MCP documentation.
Roo Code
Open Roo Code's MCP settings and add a local server named linkedin-mcp to the
global file or .roo/mcp.json, using command uvx and arguments
--from linkedin-mcp-local linkedin-mcp serve --transport stdio.
See the Roo Code MCP documentation.
Goose
Or add a custom stdio extension with command uvx and arguments
--from linkedin-mcp-local linkedin-mcp serve --transport stdio, or start one
CLI session with:
See the Goose documentation.
JetBrains AI Assistant
Open Settings → Tools → AI Assistant → Model Context Protocol (MCP), click
Add, set the command to uvx, and set the arguments to
--from linkedin-mcp-local linkedin-mcp serve --transport stdio.
See the JetBrains MCP documentation.
Continue
Create .continue/mcpServers/linkedin-mcp.json with a local server named
linkedin-mcp, command uvx, and arguments
--from linkedin-mcp-local linkedin-mcp serve --transport stdio.
See the Continue MCP documentation.
Warp
Open Settings → AI → Manage MCP Servers → Add, name the server
linkedin-mcp, set the command to uvx, and set the arguments to
--from linkedin-mcp-local linkedin-mcp serve --transport stdio.
See the Warp MCP documentation.
💡 Examples
Find jobs
Research people
Research companies
Explore posts
Manage your network
Send messages
🏗️ Architecture
Everything runs locally. There is no hosted backend, telemetry, database, external queue, LangGraph runtime, or credential service. Browser cookies live only in the local Playwright profile. The first client starts one shared local runtime; later clients attach to it, and fair scheduling gives each client a turn between complete tool calls. Operation state lasts only for that runtime. Read the full architecture and privacy policy.
🔒 Privacy Policy
The server has no maintainer-operated backend, analytics, advertising, or telemetry. LinkedIn receives normal visible-UI requests, and the invoking MCP client receives tool results under its own data policy; the project sends nothing to the maintainer. Read the complete privacy policy for processing, storage, sharing, retention, and deletion details.
🛡️ Safety
Use of this software is at your own risk. You are solely responsible for complying with LinkedIn's User Agreement, applicable laws, and third-party rights. LinkedIn may limit or restrict accounts that use prohibited automation. The maintainers do not authorize spam, unauthorized data collection, privacy violations, or circumvention of access controls.
- Use only accounts and activity you are authorized to operate.
- The server pauses on authentication expiry, checkpoints, restriction pages, permission failures, and configuration errors.
- It does not implement CAPTCHA bypass, proxy rotation, fingerprint spoofing, credential harvesting, stealth plugins, or private LinkedIn endpoints.
- Never commit or share the persistent browser profile or local assets.
See SECURITY.md and the security design.
📚 More documentation
- Configuration
- Capability matrix
- Architecture
- Testing
- Collection verification
- Distribution and registry coverage
- Publishing
- Changelog
❤️ Support the project
If LinkedIn MCP Server is useful to you:
🌐 Let's connect
Have feedback or an idea for LinkedIn MCP Server?
⚖️ License
Licensed under the Apache License 2.0.
Source: README.md at commit 0027edc
Tools
0Version history
1- v0.16.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts