# LinkedIn [Health: Active]

**Category:** 🌐 Social Media  
**Repository:** https://github.com/JohannsenLum/linkedin-api-mcp  
**GitHub Stars:** 4  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/linkedin

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

## Tools
Capabilities this server exposes over MCP:

- **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.
- **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](#safety).

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

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

## Documentation

## What the LinkedIn MCP server does

The LinkedIn MCP server gives an MCP-compatible AI client access to LinkedIn through a browser session associated with your account. It can retrieve member profiles by URL or public identifier, inspect your own profile, search for people, and look up company pages. Company results include details such as about information, size, industry, and recent posts.

Job discovery is supported through keyword and optional location searches, with a separate tool for retrieving a complete job posting. The server can also search LinkedIn feed posts. For messaging, it lists recent inbox thread previews, retrieves the full history for a selected thread, and searches conversations by participant or keyword.

Two actions change account state: `send_message` sends a real LinkedIn message, and `connect` sends a real connection invitation. They are kept separate from the read tools so an agent can distinguish account changes from information retrieval.

## How it works

The LinkedIn MCP server runs a headless Chromium browser using Patchright, an undetected Playwright fork. It uses the `li_at` session cookie from an existing LinkedIn login. This is browser-session access, not a LinkedIn API integration, credential-stuffing flow, or separate scraping API.

All operations use one browser session and run one at a time. Requests are paced according to limits configured by the user. The `linkedin_status` tool checks whether the session remains valid and reports current usage against those limits.

## Setup and configuration

Install the server with `uvx linkedin-api-mcp`. Before using it, install the Chromium build required by the server with `uvx --from linkedin-api-mcp patchright install chromium`. Log in to LinkedIn in a regular browser, copy the value of the `li_at` cookie from the LinkedIn site’s application storage, and provide it through `uvx linkedin-api-mcp auth`.

By default, authentication data is stored in the operating system keyring: Keychain on macOS, Credential Manager on Windows, or Secret Service on Linux. The server also supports passing the cookie as `LINKEDIN_COOKIE`, which can be useful in sandboxed environments or CI. Treat that value as equivalent to a login credential and protect any configuration file containing it.

Run `uvx linkedin-api-mcp --test` to confirm that LinkedIn accepts the session. The command prints redacted configuration details and does not print the cookie. Client configuration uses a stdio command with `uvx` and `linkedin-api-mcp`; documented configurations are available for Claude Code, Claude Desktop, Cursor, VS Code, Codex CLI, Zed, and Windsurf.

## Tools and capabilities

The LinkedIn MCP server provides tools for:

- Reading member profiles and the logged-in member’s profile.
- Searching people, companies, jobs, and posts.
- Reading company details and full job postings.
- Listing, searching, and opening message conversations.
- Sending a message or connection invitation.
- Checking session validity and usage status.

These capabilities suit research, recruiting workflows, job discovery, and inbox-oriented tasks where the agent must work with data visible to the logged-in account.

## Limitations and notes

The session cookie grants access as the associated LinkedIn account. Anyone who obtains it may be able to read that account’s messages and visible LinkedIn data, send messages, and send invitations. Do not place it in prompts, source control, screenshots, issues, or shared configuration.

This is an independent community project and is not affiliated with, authorized by, endorsed by, or sponsored by LinkedIn Corporation or Microsoft. The cookie-based approach also means that access depends on the browser session remaining valid and on what the account can see. Write tools perform real account actions, so clients should obtain appropriate confirmation before using them.

_Full upstream README: https://allmcps.com/mcp/linkedin/readme_