LinkedIn API MCP

Disclaimer: This is an independent, community project. It is not affiliated with, authorized by, endorsed by, or sponsored by LinkedIn Corporation or Microsoft. "LinkedIn" is a registered trademark of LinkedIn Corporation and is used here only descriptively to identify the third-party service this software interoperates with.

Documentation:mcp.johannsenlum.com/linkedin

claude mcp add linkedin -- uvx linkedin-api-mcp

{ "mcpServers": { "linkedin": { "command": "uvx", "args": ["linkedin-api-mcp"] } } }

Fallback for the button above, or if you'd rather paste it directly:

{ "mcpServers": { "linkedin": { "command": "uvx", "args": ["linkedin-api-mcp"] } } }

Fallback for the button above, or if you'd rather paste it directly. Note VS Code uses aserverskey, notmcpServers:

{ "servers": { "linkedin": { "type": "stdio", "command": "uvx", "args": ["linkedin-api-mcp"] } } }

[mcp_servers.linkedin] command = "uvx" args = ["linkedin-api-mcp"]

Codex CLI's config schema has changed across versions and this block is not independently verified against a live install. If it doesn't load, the reliable path is runninguvx linkedin-api-mcpyourself and pointing Codex at whatever its current stdio-server config expects.

No deeplink exists for Zed. Add this undercontext_serversin your Zed settings:

{ "context_servers": { "linkedin": { "source": "custom", "command": "uvx", "args": ["linkedin-api-mcp"] } } }

No deeplink exists for Windsurf. It only resolves servers from its own registry, so this has to be pasted in manually viaWindsurf Settings → MCP Servers → Edit raw config:

{ "mcpServers": { "linkedin": { "command": "uvx", "args": ["linkedin-api-mcp"] } } }

- One-time: install the Chromium build the server drives.

uvx --from linkedin-api-mcp patchright install chromium

14 tools: 12 read, 2 write.send_messageandconnectare the only two that change anything, and both are visible to another real person the moment they run: there is no draft, preview, or undo step. Everything else only reads what your account can already see. Covered by 68 tests.

What's verified, and what isn't

This is a days-old project. Rather than claim everything works, here's what's actually been checked against a live account, and what hasn't.

-

A serialised action queue.Every tool call, includinglinkedin_status, passes through the same queue before it touches the browser: one action at a time, never in parallel.

A minimum interval and an hourly ceiling, both enforced, not just claimed:

The ceiling is local to this server: it exists to stop a looping agent from generating a burst of LinkedIn traffic, not because LinkedIn told us these numbers. Lowering them is always safe; raising them is you deciding you're willing to accept more risk than the defaults assume.

Prompt-injection fencing on all scraped free text.Anything read off a LinkedIn page (a headline, an about section, a message) passes through your agent as data. It is fenced before your agent sees it, so text on a profile or in a message cannot pose as an instruction.

send_messageproves delivery before reporting success.It polls the conversation until the sent text actually appears, and raisessend_unconfirmedrather than a false{"sent": true}if it doesn't.

This tool controls a real browser session; it doesn't exploit undocumented APIs or bypass authentication. LinkedIn's User Agreement prohibits automated access, and accounts using automated tools can be restricted or banned. Use at your own risk; there is no guarantee of account safety. If you encounter any issues, let me know in the Discussions.

What if my agents execute too many actions?

Tool calls run sequentially through a queue. You are responsible for the volume of automation you run; use it sparingly and prompt your agents responsibly.

Use it, change it, redistribute it, build something commercial on it: the only condition is that you keep the copyright notice and licence text. It comes with no warranty of any kind.

Contributions are accepted under the same licence.

Issues and pull requests are welcome:github.com/JohannsenLum/linkedin-api-mcp. Changes are recorded inCHANGELOG.md.

pip install -e ".[dev]" python -m pytest -q

This is an independent project, not affiliated with LinkedIn Corporation. See the disclaimer at the top of this document.

Manage your WhatsApp, SMS and Phone Calls using a single MCP connector

Connect to any function, any language, across network boundaries using AgentRPC.

Access your meeting transcripts, summaries, and action items from any AI assistant.

Connect Claude, ChatGPT, and other AI tools to your Granola meeting notes via MCP. Query your notes, search transcripts, and get meeting insights in your favorite AI assistants.

Build with the Kudosity API to send SMS and MMS. Access developer docs, API references and live testing tools to send messages, manage contact lists, configure webhooks and more.

Send SMS, WhatsApp, and RCS messages programmatically with DLT compliance. Manage contacts, schedule campaigns, and track delivery reports.

Interact with Twilio APIs to send messages, manage phone numbers, configure your account, and more.

The VoIPstudio MCP server gives compatible AI assistants secure access to authorised VoIPstudio account data, including recordings, call detail records, live calls and voicemails in order to query call activity, analyse patterns, identify agent performance issues and generate QA or operations reports in plain English.

A bridge server connecting Agent Communication Protocol (ACP) agents with Model Context Protocol (MCP) clients.