Read LinkedIn profiles, companies, jobs and messages via your own browser session

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

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

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Capabilities & Tool Schemas (12)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by LinkedIn.

get_profile

Fetch a member's profile (headline, about, experience, education, skills) by URL or public identifier.

get_my_profile

Fetch the profile of the account this server is logged in as.

search_people

Search LinkedIn members by keyword.

get_inbox

List recent message thread previews.

get_conversation

Fetch the full message history of one thread, by id.

search_conversations

Search your message threads by participant or keyword.

Documentation Overview

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.

An MCP server for LinkedIn. It drives a real, headless browser (patchright, an undetected fork of Playwright) using your own logged-in LinkedIn session cookie. There is no scraping API, no credential stuffing, no bypass of LinkedIn's login. Your agent gets 12 read tools (profiles, companies, jobs, posts, your inbox) and two write tools, kept deliberately separate: sending a message and sending a connection request. Every action goes through a single browser session, one at a time, paced against limits you control. See Safety below.

Documentation: mcp.johannsenlum.com/linkedin

Install (one-click)

Deeplinks exist for Cursor and VS Code only; no other client has a documented install-link format. These prefill the command below, nothing else needs filling in since the cookie lives in your OS keyring, not an environment variable.

All clients

Client	Deeplink?
Claude Code	no, one-line command
Claude Desktop	no
Cursor	yes, above
VS Code	yes, above
Codex CLI	no
Zed	no
Windsurf	no (Windsurf only resolves servers in its own registry)

Claude Code

Terminal

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

Claude Desktop: claude_desktop_config.json

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

No one-click install exists for Claude Desktop (it installs .mcpb bundles, not deeplinks). Copy this JSON in via Settings → Developer → Edit Config:

JSON Config

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

Cursor: ~/.cursor/mcp.json

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

JSON Config

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

VS Code: .vscode/mcp.json

Fallback for the button above, or if you'd rather paste it directly. Note VS Code uses a servers key, not mcpServers:

JSON Config

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

Codex CLI: ~/.codex/config.toml

toml

[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 running uvx linkedin-api-mcp yourself and pointing Codex at whatever its current stdio-server config expects.

Zed: settings.json

No deeplink exists for Zed. Add this under context_servers in your Zed settings:

JSON Config

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

Windsurf: ~/.codeium/windsurf/mcp_config.json

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

JSON Config

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

If you'd rather not rely on the keyring in a given client (a sandboxed environment, or CI), pass the cookie directly instead of running auth:

JSON Config

{
  "mcpServers": {
    "linkedin": {
      "command": "uvx",
      "args": ["linkedin-api-mcp"],
      "env": { "LINKEDIN_COOKIE": "your-li_at-value" }
    }
  }
}

Anywhere you do this, treat that config file with the same care as the cookie itself: don't commit it, and restrict its permissions.

Getting your session cookie

LinkedIn doesn't offer an API key for this kind of access, so the server uses the same session cookie your browser already holds.

One-time: install the Chromium build the server drives.
bash
```
uvx --from linkedin-api-mcp patchright install chromium
```
Log in to linkedin.com in a normal browser.
Open DevTools (F12 or Cmd+Opt+I) → Application → Cookies → https://www.linkedin.com.
Find the row named li_at and copy its Value.

[!WARNING] This cookie is your LinkedIn login. Anyone who has it can act as you: read your messages, message your connections, see everything your account can see, without needing your password. It survives a password change, and it cannot be revoked from any session list LinkedIn shows you. Never paste it into a chat, a commit, an issue, a screenshot, or anywhere other than linkedin-api-mcp auth.

Store it:
bash
```
uvx linkedin-api-mcp auth
```
Paste the value in when prompted; the terminal will not echo it back. By default it's stored in your OS keyring (Keychain, Windows Credential Manager, or Secret Service on Linux), never written to a config file.
Verify LinkedIn accepts it before wiring up a client:
bash
```
uvx linkedin-api-mcp --test
```
Prints the server's redacted configuration and confirms the session is live. It never prints the cookie itself.

Tools

Tool	Description
`get_profile`	Fetch a member's profile (headline, about, experience, education, skills) by URL or public identifier.
`get_my_profile`	Fetch the profile of the account this server is logged in as.
`search_people`	Search LinkedIn members by keyword.
`get_inbox`	List recent message thread previews.
`get_conversation`	Fetch the full message history of one thread, by id.
`search_conversations`	Search your message threads by participant or keyword.
`send_message` ✏️	Write. Sends a real message to another member from your account.
`connect` ✏️	Write. Sends a real connection invitation to another member from your account.
`get_company`	Fetch a company page (about, size, industry, recent posts).
`search_companies`	Search LinkedIn companies by keyword.
`search_jobs`	Search job postings by keyword and optional location.
`get_job`	Fetch one job posting in full.
`search_posts`	Search LinkedIn feed posts by keyword.
`linkedin_status`	Check session validity and current usage against the rate limits in Safety.

14 tools: 12 read, 2 write. send_message and connect are 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.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Social Media View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

1mo ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about LinkedIn

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "linkedin": { "command": "uvx", "args": ["linkedin-api-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/linkedin?style=directory)](https://allmcps.com/mcp/linkedin)

HTML Embed

<a href="https://allmcps.com/mcp/linkedin"><img src="https://allmcps.com/api/badge/linkedin?style=directory" alt="LinkedIn on AllMCPs" /></a>

Technical Specs & Signals

CategorySocial Media

4/6 checks healthy over the last 45d

51Quality signal: Good · 51/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools25/30

Adoption & activity3/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · linkedin-api-mcp (PyPI)

★ Featured

AllMCPs Server

The official MCP server for AllMCPs.com - submit and manage tools directly from your AI. The open directory for MCP servers. Connect Claude, Cursor, Windsurf, and AI agents to databases, tools, files, and APIs. Explore 10,000+ servers. AllMCPs is the premier, open directory for discovering, evaluating, and installing Model Context Protocol (MCP) servers to equip AI agents and LLMs with real-world superpowers.

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🌐 Social Media →Best MCP servers for Social Media →Alternatives to LinkedIn →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients

Read LinkedIn profiles, companies, jobs and messages via your own browser session

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

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

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Capabilities & Tool Schemas (12)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by LinkedIn.

get_profile

Fetch a member's profile (headline, about, experience, education, skills) by URL or public identifier.

get_my_profile

Fetch the profile of the account this server is logged in as.

search_people

Search LinkedIn members by keyword.

get_inbox

List recent message thread previews.

get_conversation

Fetch the full message history of one thread, by id.

search_conversations

Search your message threads by participant or keyword.

Documentation Overview

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

Install (one-click)

All clients

Client	Deeplink?
Claude Code	no, one-line command
Claude Desktop	no
Cursor	yes, above
VS Code	yes, above
Codex CLI	no
Zed	no
Windsurf	no (Windsurf only resolves servers in its own registry)

Claude Code

Terminal

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

Claude Desktop: claude_desktop_config.json

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

No one-click install exists for Claude Desktop (it installs .mcpb bundles, not deeplinks). Copy this JSON in via Settings → Developer → Edit Config:

JSON Config

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

Cursor: ~/.cursor/mcp.json

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

JSON Config

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

VS Code: .vscode/mcp.json

Fallback for the button above, or if you'd rather paste it directly. Note VS Code uses a servers key, not mcpServers:

JSON Config

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

Codex CLI: ~/.codex/config.toml

toml

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

Zed: settings.json

No deeplink exists for Zed. Add this under context_servers in your Zed settings:

JSON Config

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

Windsurf: ~/.codeium/windsurf/mcp_config.json

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

JSON Config

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

If you'd rather not rely on the keyring in a given client (a sandboxed environment, or CI), pass the cookie directly instead of running auth:

JSON Config

{
  "mcpServers": {
    "linkedin": {
      "command": "uvx",
      "args": ["linkedin-api-mcp"],
      "env": { "LINKEDIN_COOKIE": "your-li_at-value" }
    }
  }
}

Anywhere you do this, treat that config file with the same care as the cookie itself: don't commit it, and restrict its permissions.

Getting your session cookie

LinkedIn doesn't offer an API key for this kind of access, so the server uses the same session cookie your browser already holds.

One-time: install the Chromium build the server drives.
bash
```
uvx --from linkedin-api-mcp patchright install chromium
```
Log in to linkedin.com in a normal browser.
Open DevTools (F12 or Cmd+Opt+I) → Application → Cookies → https://www.linkedin.com.
Find the row named li_at and copy its Value.

[!WARNING] This cookie is your LinkedIn login. Anyone who has it can act as you: read your messages, message your connections, see everything your account can see, without needing your password. It survives a password change, and it cannot be revoked from any session list LinkedIn shows you. Never paste it into a chat, a commit, an issue, a screenshot, or anywhere other than linkedin-api-mcp auth.

Store it:
bash
```
uvx linkedin-api-mcp auth
```
Paste the value in when prompted; the terminal will not echo it back. By default it's stored in your OS keyring (Keychain, Windows Credential Manager, or Secret Service on Linux), never written to a config file.
Verify LinkedIn accepts it before wiring up a client:
bash
```
uvx linkedin-api-mcp --test
```
Prints the server's redacted configuration and confirms the session is live. It never prints the cookie itself.

Tools

Tool	Description
`get_profile`	Fetch a member's profile (headline, about, experience, education, skills) by URL or public identifier.
`get_my_profile`	Fetch the profile of the account this server is logged in as.
`search_people`	Search LinkedIn members by keyword.
`get_inbox`	List recent message thread previews.
`get_conversation`	Fetch the full message history of one thread, by id.
`search_conversations`	Search your message threads by participant or keyword.
`send_message` ✏️	Write. Sends a real message to another member from your account.
`connect` ✏️	Write. Sends a real connection invitation to another member from your account.
`get_company`	Fetch a company page (about, size, industry, recent posts).
`search_companies`	Search LinkedIn companies by keyword.
`search_jobs`	Search job postings by keyword and optional location.
`get_job`	Fetch one job posting in full.
`search_posts`	Search LinkedIn feed posts by keyword.
`linkedin_status`	Check session validity and current usage against the rate limits in Safety.

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.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Social Media View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

1mo ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about LinkedIn

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "linkedin": { "command": "uvx", "args": ["linkedin-api-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/linkedin?style=directory)](https://allmcps.com/mcp/linkedin)

HTML Embed

<a href="https://allmcps.com/mcp/linkedin"><img src="https://allmcps.com/api/badge/linkedin?style=directory" alt="LinkedIn on AllMCPs" /></a>

Technical Specs & Signals

CategorySocial Media

4/6 checks healthy over the last 45d

51Quality signal: Good · 51/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools25/30

Adoption & activity3/15

Community engagement0/10

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · linkedin-api-mcp (PyPI)

★ Featured

AllMCPs Server

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🌐 Social Media →Best MCP servers for Social Media →Alternatives to LinkedIn →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients