MCP Server for LinkedIn

<!-- mcp-name: io.github.stickerdaniel/linkedin-mcp-server --> <p align="left"> <a href="https://pypi.org/project/mcp-server-linkedin/" target="_blank"><img src="https://img.shields.io/pypi/v/mcp-server-linkedin?color=blue" alt="PyPI"></a> <a href="https://github.com/stickerdaniel/linkedin-mcp-server/actions/workflows/ci.yml" target="_blank"><img src="https://github.com/stickerdaniel/linkedin-mcp-server/actions/workflows/ci.yml/badge.svg?branch=main" alt="CI Status"></a> <a href="https://github.com/stickerdaniel/linkedin-mcp-server/actions/workflows/release.yml" target="_blank"><img src="https://github.com/stickerdaniel/linkedin-mcp-server/actions/workflows/release.yml/badge.svg?branch=main" alt="Release"></a> <a href="https://github.com/stickerdaniel/linkedin-mcp-server/blob/main/LICENSE" target="_blank"><img src="https://img.shields.io/badge/License-Apache%202.0-%233fb950?labelColor=32383f" alt="License"></a> </p>

An MCP server that connects AI assistants like Claude to LinkedIn through your own logged-in browser session. Look up profiles and companies, send messages, manage your inbox, or search for jobs. All browser actions run locally on your machine.

This is an independent open-source project, not affiliated with, authorized by, endorsed by, or sponsored by LinkedIn or Microsoft. LinkedIn is a trademark of LinkedIn Corporation and is used here only to identify the service this software interacts with.

<br/> <details open> <summary><strong>LinkedIn MCP Sponsor</strong></summary> <br/> <a href="https://golink.onl/unipile-banner" target="_blank"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://github.com/user-attachments/assets/c2e7f3b4-6812-4f28-8728-10f882a44e0e"> <img src="https://github.com/user-attachments/assets/89ab8932-ae79-41c2-8416-a699e924218b" alt="Unipile, one API for every LinkedIn feature" width="100%"> </picture> </a>

This MCP server is supported by Unipile. Unipile is the fully managed cloud option for developers: a hosted LinkedIn API for Classic, Sales Navigator, and Recruiter that handles auth, sessions, and infrastructure for you.

Try Unipile free for 7 days →

</details>

---

<a id="installation-methods"></a>

Installation Methods - LinkedIn MCP Server

| Tool | Description | |------|-------------| | get_person_profile | Read profile sections such as experience, education, skills, projects and posts. | | get_my_profile | Read your own profile using the same selectable sections. | | connect_with_person | Send or accept a connection request, with an optional note. | | get_sidebar_profiles | Find recommended profile links in a person's sidebar. | | get_inbox | List recent messaging conversations from your LinkedIn inbox. | | get_conversation | Read a conversation by username or thread ID. | | search_conversations | Search messages by keyword across your conversations. | | send_message | Send after confirmation. Targeting a profile may start a separate DM instead of replying in a thread (#483). | | get_company_profile | Read posts and jobs; about references can include a company_urn for the currentCompany search facet. | | get_company_posts | Read recent posts published on a company's LinkedIn page. | | search_companies | Find LinkedIn company profiles matching a keyword search. | | get_company_employees | List company employees, optionally filtered by keyword. | | search_jobs | Find LinkedIn job postings by keyword and location. | | get_saved_jobs | List the job postings you have saved on LinkedIn. | | search_people | Search by keyword, location, connection degree or company. | | get_job_details | Read the details of a LinkedIn job posting by its job ID. | | get_feed | Read recent home-feed posts, with links in references. | | search_posts | Search posts by keyword with optional recency filters; references contains unordered candidate post links. | | close_session | Close the active browser session and release its resources. |

<br/> <br/>

Setup with uvx (Recommended)

Prerequisites: Install uv.

Installation

Client Configuration

{
  "mcpServers": {
    "mcp-server-linkedin": {
      "command": "uvx",
      "args": ["mcp-server-linkedin@latest"],
      "env": { "UV_HTTP_TIMEOUT": "300" }
    }
  }
}

The @latest tag turns on automatic updates, which keep the server working with LinkedIn's current page structure. The server starts quickly, prepares the shared Patchright Chromium browser cache in the background under ~/.linkedin-mcp/patchright-browsers, and opens a LinkedIn login browser window on the first tool call that needs authentication.

AI agent? Get a quick confirmation from the user before enabling automatic updates.

[!NOTE] Early tool calls may return a setup/authentication-in-progress error until browser setup or login finishes. If you prefer to create a session explicitly, run uvx mcp-server-linkedin@latest --login.

Setup Help

<details> <summary><b>🔧 Configuration</b></summary> <details> <summary>Transport modes</summary>

• Default (stdio): Standard communication for local MCP servers
• Streamable HTTP: For a web-based MCP server
• If no transport is specified, the server defaults to stdio
• An interactive terminal without explicit transport shows a chooser prompt

</details> <details> <summary>CLI options</summary>

Session:

• --login - Open a browser to sign in and save the session
• --import-from-browser [BROWSER] - Reuse a session from a locally signed-in Chromium browser (chrome, chromium, brave, edge, arc, vivaldi, helium, yandex, whale, auto). Bare flag picks auto, the most recently used browser with a live LinkedIn session.
• --auto-import / --no-auto-import - Import a session from a signed-in local browser on the first tool call that needs one, before falling back to manual login (default: on). Skipped in Docker, behind a proxy, and on a non-loopback HTTP bind. On macOS the keychain may prompt once.
• --logout - Clear the stored session
• --login-viewer - Docker only: show the --login browser at a token-protected URL on port 6080 (see Authentication)
• --user-data-dir PATH - Browser profile directory (default: ~/.linkedin-mcp/profile). Rotating or clearing a session deletes this directory and its parent, which holds the stored cookies and derived profiles.
• --claim-profile-root - Take over a profile directory the server will not claim on its own, such as one whose parent already holds other files. Needed once per directory.

Transport:

• --transport {stdio,streamable-http} - Force the transport mode (default: stdio)
• --host HOST / --port PORT / --path PATH - HTTP server address (defaults: 127.0.0.1, 8000, /mcp)

Timeouts:

• --timeout MS - Timeout for a single page operation (default: 5000)
• --tool-timeout SECONDS - Timeout for a whole tool call (default: 180). Raise it for heavy scrapes, slow networks, or a cold-start browser.
• --login-timeout SECONDS - How long the login browser waits for you to finish signing in (default: 1800; 0 = no limit). --login-viewer ends the session after 30 minutes either way.
• --login-inline-wait SECONDS - How long a tool call waits for a login to finish before telling the model to retry (default: 25, max 45; 0 = return at once)

Shared browser:

• --browser-wait SECONDS - How long to wait for another server process to hand over the shared browser (default: 25, max 45; 0 = report busy at once). Only matters with several MCP clients running at once.
• --browser-min-hold SECONDS - Shortest time this process keeps the shared browser before handing it over (default: 20). Clamped to 3 seconds below --browser-wait, so raise that one along with it. Higher means fewer browser restarts but longer waits for other clients.
• --browser-idle-timeout SECONDS - Close an idle browser and release the profile after this long without a tool call (default: 600; 0 = keep it open)

Browser:

• --no-headless - Show the browser window (useful for debugging)
• --chrome-path PATH - Path to a Chrome/Chromium executable
• --proxy-server URL - Route browser traffic through a proxy, as scheme://host:port. Set it up before --login; see Using a proxy.

Other:

• --log-level {DEBUG,INFO,WARNING,ERROR} - Logging level (default: WARNING)

</details> <details> <summary>Import a session from your everyday browser</summary>

If you are already signed into LinkedIn in Chrome, Chromium, Brave, Edge, Arc, Vivaldi, Helium, Yandex, or Naver Whale, you can skip the manual --login step and reuse that session:

# Auto-pick the most recently used browser