# LinkedIn MCP server

> Lets an AI client read LinkedIn profiles, jobs, companies, feed and messages as structured JSON and perform confirmed write actions.

- Repository: https://github.com/devag7/linkedin-mcp
- Page: https://hostedmcp.org/servers/devag7/linkedin-mcp
- Transport: stdio
- Stars: 12
- License: MIT
- Latest version: 4.4.0

## Install

### Claude Code

```sh
claude mcp add linkedin-mcp -- npx -y linkedin-mcp-tools
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "linkedin-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "linkedin-mcp-tools"
      ]
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "linkedin-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "linkedin-mcp-tools"
      ]
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"linkedin-mcp","type":"stdio","command":"npx","args":["-y","linkedin-mcp-tools"]}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "linkedin-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "linkedin-mcp-tools"
      ]
    }
  }
}
```

### Codex

```sh
codex mcp add linkedin-mcp -- npx -y linkedin-mcp-tools
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.linkedin-mcp]
command = "npx"
args = ["-y", "linkedin-mcp-tools"]
```

### Gemini CLI

```sh
gemini mcp add -s user linkedin-mcp npx -- -y linkedin-mcp-tools
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "linkedin-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "linkedin-mcp-tools"
      ]
    }
  }
}
```

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `LINKEDIN_HTTP_TOKEN` | no | no |  |

## Tools (24)

- `whoami`: Report server version, browser/login status, and capabilities. (read-only)
- `health_check`: Deep health check: cookie login state, a LIVE Voyager probe (confirms the API actually answers, not just that a cookie exists), and today's safety-budget headroom (per-action used/cap/remaining + pending invites). (read-only)
- `close_session`: Close Chrome while retaining this runtime’s profile ownership. Stop the server to release the profile.
- `get_my_profile`: Get the authenticated user's own LinkedIn profile (experience, education, headline, summary). (read-only)
- `get_profile`: Get a LinkedIn profile by public identifier (the slug in the profile URL, e.g. "satyanadella"). (read-only)
- `get_feed`: Get recent posts from your LinkedIn home feed (author + post text). (read-only)
- `get_notifications`: Get your recent LinkedIn notifications (headline, time, read state). (read-only)
- `search_people`: Search LinkedIn people by keywords. Returns name, headline, location, and public identifier (pass that to get_profile for full details). (read-only)
- `search_jobs`: Search LinkedIn jobs by keywords (and optional location). Returns title, location, posted time. (read-only)
- `get_inbox`: List a bounded first page of recent conversations with participant names, headlines and profile links. Continuation is not verified. (read-only)
- `get_job_details`: Get full details for a job posting by its numeric id (the digits in /jobs/view/<id> or from search_jobs jobUrn). (read-only)
- `search_companies`: Search LinkedIn companies by keywords. Returns name + universalName slug (pass that to get_company for full details). (read-only)
- `get_company`: Get a company by its LinkedIn URL slug (e.g. "google", "microsoft"). Returns name, description, website, industry, size, HQ. (read-only)
- `get_company_posts`: Get a company's recent posts by its LinkedIn URL slug (e.g. "google"). Returns post text + a short meta line. (read-only)
- `get_company_employees`: List employees LinkedIn surfaces for a company (by URL slug). Returns name, headline, and public identifier (feed the slug to get_profile). Prospecting core. (read-only)
- `get_pending_invitations`: List your pending connection invitations — received (inbound, with the urn/sharedSecret to accept later) and sent (outbound). Read-only. (read-only)
- `get_conversation`: Read a bounded page of messages by the conversation URN from get_inbox, sorted oldest-first with sender attribution when present. Continuation is not verified. (read-only)
- `prepare_job_application`: Create a local, unsaved application worksheet with optional reusable evidence, resume/cover-letter drafts and interview practice when supported by the input schema. Only explicitly selected user-supplied evidence is used; nothing is fetched, filled, uploaded, submitted, sent or stored. Verify every claim and the current listing yourself. (read-only)
- `export_application_tracker`: Format up to 50 application statuses that you enter into a CSV. Optionally classify follow-up dates against your explicit as_of time; no notifications are scheduled. It does not inspect LinkedIn, infer submission, or save data. A receipt-verified status requires your explicit confirmation. (read-only)
- `connect_with_person`: [ALPHA, write] Send a connection request. Gated: requires confirm:true. Returns a structured status (ok | duplicate | already_connected | restricted | quota_exhausted | failed | unknown). Counts against the daily connect cap.
- `send_message`: [ALPHA, write] Send a message. Pass thread_id / conversation_urn to REPLY into an existing conversation; new threads require a separate experimental opt-in and lack current live success evidence. Gated: requires confirm:true. Returns a structured status. Counts against the daily message cap.
- `create_post`: [ALPHA, write] Publish a text post to your feed. Gated: requires confirm:true. Returns a structured status.
- `react_to_post`: [ALPHA, write] React to a post. Gated: requires confirm:true. Returns a structured status.
- `comment_on_post`: [ALPHA, write] Comment on a post. Gated: requires confirm:true. Returns a structured status.

## FAQ

### What can an AI assistant do with the LinkedIn MCP server?

It can read profiles, run people/job/company searches, and pull feed and inbox data as structured JSON, plus optional gated write actions.

### How does the LinkedIn MCP server access LinkedIn data?

It opens a persistent Chrome profile via Patchright and makes Voyager requests from the authenticated page, shaping results into JSON.

### Do I need to log in to LinkedIn to use it?

Yes, you log in once in a real Chrome window, and the session persists to a local profile directory.

### Are write actions like messaging or posting enabled by default?

No, alpha writes are disabled by default and require a preview token plus confirm:true when enabled.

### Can this server fill out or submit job applications?

No, it does not fill or submit applications, including Easy Apply, though it can prepare draft materials.
