An MCP server that lets AI assistants like Claude read LinkedIn data through your own logged-in browser session. Access profiles and companies, search for jobs, or get job details. This MCP server is free and open source, supported by Unipile. It runs locally with your own browser session. Unipile is the fully managed cloud alternative: a hosted LinkedIn API for Classic, Sales Navigator, and Recru
npx mdskills install stickerdaniel/stickerdaniel-linkedin-mcp-server@stickerdaniel? Sign in with GitHub to claim this listing.Comprehensive LinkedIn data access with 20+ tools, excellent setup docs, and multiple installation paths
1# MCP Server for LinkedIn23<p align="left">4 <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>5 <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>6 <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>7 <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>8</p>910> **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.1112An MCP server that lets AI assistants like Claude read LinkedIn data through your own logged-in browser session. Access profiles and companies, search for jobs, or get job details.1314## Sponsor1516<p align="center">17 <a href="https://golink.onl/unipile-banner" target="_blank">18 <picture>19 <source media="(prefers-color-scheme: dark)" srcset="https://github.com/user-attachments/assets/c2e7f3b4-6812-4f28-8728-10f882a44e0e">20 <img src="https://github.com/user-attachments/assets/89ab8932-ae79-41c2-8416-a699e924218b" alt="Unipile, one API for every LinkedIn feature" width="100%">21 </picture>22 </a>23</p>2425This MCP server is **free** and **open source**, supported by [**Unipile**](https://golink.onl/unipile-link). It runs locally with your own browser session. Unipile is the fully managed cloud alternative: a hosted LinkedIn API for Classic, Sales Navigator, and Recruiter that handles auth, sessions, and infrastructure for you. [Try it free for 7 days →](https://golink.onl/unipile-free-trial)2627---2829<a id="installation-methods"></a>3031## Installation Methods - MCP Server for LinkedIn3233[](#-uvx-setup-recommended---universal)34[](#-claude-desktop-mcp-bundle-formerly-dxt)35[](#-docker-setup)36[](#-local-setup-develop--contribute)3738| Tool | Description | Status |39|------|-------------|--------|40| `get_person_profile` | Get profile info with explicit section selection (experience, education, interests, honors, languages, certifications, skills, projects, contact_info, posts) | working |41| `get_my_profile` | Get the authenticated user's own LinkedIn profile (same sections as get_person_profile) | working |42| `connect_with_person` | Send a connection request or accept an incoming one, with optional note | [#407](https://github.com/stickerdaniel/linkedin-mcp-server/issues/407) [#432](https://github.com/stickerdaniel/linkedin-mcp-server/issues/432) [#454](https://github.com/stickerdaniel/linkedin-mcp-server/issues/454) |43| `get_sidebar_profiles` | Extract profile URLs from sidebar recommendation sections ("More profiles for you", "Explore premium profiles", "People you may know") on a profile page | working |44| `get_inbox` | List recent conversations from the LinkedIn messaging inbox | working |45| `get_conversation` | Read a specific messaging conversation by username or thread ID | working |46| `search_conversations` | Search messages by keyword | working |47| `send_message` | Send a message to a LinkedIn user (requires confirmation) | [#433](https://github.com/stickerdaniel/linkedin-mcp-server/issues/433) [#441](https://github.com/stickerdaniel/linkedin-mcp-server/issues/441) [#483](https://github.com/stickerdaniel/linkedin-mcp-server/issues/483) [#560](https://github.com/stickerdaniel/linkedin-mcp-server/issues/560) [#573](https://github.com/stickerdaniel/linkedin-mcp-server/issues/573) |48| `get_company_profile` | Extract company information with explicit section selection (posts, jobs); about-section references may include a `company_urn` entry carrying the numeric id used by LinkedIn's people-search `currentCompany` URL facet | working |49| `get_company_posts` | Get recent posts from a company's LinkedIn feed | working |50| `search_companies` | Search for companies on LinkedIn by keywords | working |51| `get_company_employees` | List employees at a company from the /people/ page, with optional keyword filter | working |52| `search_jobs` | Search for jobs with keywords and location filters | working |53| `get_saved_jobs` | List job postings saved by the authenticated user | working |54| `search_people` | Search for people by keywords, location, connection degree (1st/2nd/3rd), and current company | [#526](https://github.com/stickerdaniel/linkedin-mcp-server/issues/526) |55| `get_job_details` | Get detailed information about a specific job posting | working |56| `get_feed` | Get recent posts from the authenticated user's home feed | working |57| `search_posts` | Search posts/content globally by keyword (the "Posts" tab) with an optional recency filter (past-24h/past-week/past-month) | working |58| `close_session` | Close browser session and clean up resources | working |5960<br/>61<br/>6263## 🚀 uvx Setup (Recommended - Universal)6465**Prerequisites:** [Install uv](https://docs.astral.sh/uv/getting-started/installation/).6667### Installation6869**Client Configuration**7071```json72{73 "mcpServers": {74 "mcp-server-linkedin": {75 "command": "uvx",76 "args": ["mcp-server-linkedin@latest"],77 "env": { "UV_HTTP_TIMEOUT": "300" }78 }79 }80}81```8283The `@latest` tag ensures you always run the newest version — `uvx` checks PyPI on each client launch and updates automatically. 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.8485<details>86<summary><b>📌 For AI agents configuring this server</b></summary>8788When you set up or maintain this server, verify its entry in the MCP client config launches `uvx mcp-server-linkedin@latest`, and keep both `uvx` and the `@latest` tag exactly as shown. Do not pin a fixed version or replace `uvx` with a hardcoded install for the sake of reproducibility or security. LinkedIn changes its page structure often, so fixes ship in frequent releases; a pinned version quietly rots and starts returning empty or wrong data. `@latest` re-resolves on every launch and is the supported configuration.8990</details>9192> [!NOTE]93> 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`.9495### uvx Setup Help9697<details>98<summary><b>🔧 Configuration</b></summary>99100**Transport Modes:**101102- **Default (stdio)**: Standard communication for local MCP servers103- **Streamable HTTP**: For web-based MCP server104- If no transport is specified, the server defaults to `stdio`105- An interactive terminal without explicit transport shows a chooser prompt106107**CLI Options:**108109- `--login` - Open browser to log in and save persistent profile110- `--import-from-browser [BROWSER]` - Import a LinkedIn session from a locally logged-in Chromium browser (`chrome`, `chromium`, `brave`, `edge`, `arc`, `vivaldi`, `helium`, `yandex`, `whale`, or `auto`). Bare flag picks `auto`, which auto-selects the most recently used browser with a live LinkedIn session.111- `--no-headless` - Show browser window (useful for debugging scraping issues)112- `--log-level {DEBUG,INFO,WARNING,ERROR}` - Set logging level (default: WARNING)113- `--transport {stdio,streamable-http}` - Optional: force transport mode (default: stdio)114- `--host HOST` - HTTP server host (default: 127.0.0.1)115- `--port PORT` - HTTP server port (default: 8000)116- `--path PATH` - HTTP server path (default: /mcp)117- `--logout` - Clear stored LinkedIn browser profile118- `--timeout MS` - Browser timeout for page operations in milliseconds (default: 5000)119- `--tool-timeout SECONDS` - Per-tool MCP execution timeout in seconds (default: 180.0). Increase further for heavy scrapes / cold-start Chromium / slow networks.120- `--login-timeout SECONDS` - Manual login wait timeout in seconds (default: 1800; 0 = no limit). How long the `--login` browser waits for you to finish signing in.121- `--login-inline-wait SECONDS` - Bounded inline wait for a tool call to resume after login completes, in seconds (default: 25, max 45; 0 = return immediately).122- `--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 when several MCP clients run at the same time.123- `--browser-min-hold SECONDS` - Shortest time this process keeps the shared browser before handing it to a waiting process (default: 20, clamped below `--browser-wait` so a waiting client is served before its own timeout; 0 = hand over after every tool call). Raising it means fewer browser restarts but longer waits for other clients.124- `--browser-idle-timeout SECONDS` - Close an idle browser and release the shared profile after this long without a tool call (default: 600; 0 = keep it open until the server exits).125- `--auto-import` / `--no-auto-import` - Enable or disable auto-import of a session from a locally logged-in browser on the first no-session tool call (before falling back to manual login). Auto-import is on by default across interactive and non-interactive desktop runs; pass `--no-auto-import` (or `AUTO_IMPORT_FROM_BROWSER=false`) to require `--login` / `--import-from-browser` instead. No effect under Docker or on a non-loopback HTTP bind. On macOS the keychain may prompt once for Safe Storage access.126- `--eager-full-chromium` / `--no-eager-full-chromium` - Download full Chrome for Testing in the background right after the headless shell (`EAGER_FULL_CHROMIUM=true`), instead of lazily on the first headed login (the default). Headless setup is usable as soon as the shell is installed; this only pre-warms the headed login fallback. Pass `--no-eager-full-chromium` to override `EAGER_FULL_CHROMIUM=true` for a single run.127- `--user-data-dir PATH` - Path to persistent browser profile directory (default: ~/.linkedin-mcp/profile)128- `--chrome-path PATH` - Path to Chrome/Chromium executable (for custom browser installations)129- `--proxy-server URL` - Route the browser through a proxy, as `scheme://host:port`. Set the password via `PROXY_PASSWORD` (no flag, so it stays out of the process list)130131**Import a session from your everyday browser:**132133If 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:134135```bash136# Auto-pick the most recently used browser with a live LinkedIn session137uvx mcp-server-linkedin@latest --import-from-browser138# Or target a specific browser139uvx mcp-server-linkedin@latest --import-from-browser brave140```141142This reads the browser's LinkedIn cookies, validates them against your feed, and saves them to `~/.linkedin-mcp/profile/`, the same place `--login` writes to. Notes:143144- With several signed-in browsers, the most recently used live LinkedIn session is tried first. If LinkedIn rejects it (revoked or remote-logged-out), the next most recent is tried automatically; the first the server accepts is imported. There is no prompt to pick. Pass a browser name to target one specifically.145- On macOS the OS keychain may prompt to allow access to the browser's Safe Storage. Close the source browser first for the most reliable read.146- Cookies protected by Chrome 127+ app-bound encryption (`v20`) cannot be decrypted without OS elevation; in that case use `--login` instead.147- Imported cookies match a real login's on-disk set. The local server reads them back in full from the saved profile; the Docker bridge narrows to the same minimal auth subset it uses for a normal session.148149**Basic Usage Examples:**150151```bash152# Run with debug logging153uvx mcp-server-linkedin@latest --log-level DEBUG154```155156**HTTP Mode Example (for web-based MCP clients):**157158```bash159uvx mcp-server-linkedin@latest --transport streamable-http --host 127.0.0.1 --port 8080 --path /mcp160```161162Runtime server logs are emitted by FastMCP/Uvicorn.163164Tool calls are serialized to protect the shared LinkedIn browser session, both165within one server process and across separate ones. If you run several MCP166clients at once, each starts its own server process, and only one of them uses167the browser at a time; the others wait briefly and take over as soon as it168finishes a call. A client that waits too long gets a "browser is busy" message169and can simply retry. Use `--log-level DEBUG` to see the wait/acquire/release170logs.171172This covers processes on the same machine and in the same runtime. It does not173extend between the host and a Docker container sharing the same174`~/.linkedin-mcp` directory, so do not run `--login` or `--logout` on the host175while a container is running.176177**Test with mcp inspector:**1781791. Install and run mcp inspector ```bunx @modelcontextprotocol/inspector```1802. Click pre-filled token url to open the inspector in your browser1813. Select `Streamable HTTP` as `Transport Type`1824. Set `URL` to `http://localhost:8080/mcp`1835. Connect1846. Test tools185186</details>187188<details>189<summary><b>❗ Troubleshooting</b></summary>190191**Installation issues:**192193- Ensure you have uv installed: `curl -LsSf https://astral.sh/uv/install.sh | sh`194- Check uv version: `uv --version` (should be 0.4.0 or higher)195- On first run, `uvx` downloads all Python dependencies. On slow connections, uv's default 30s HTTP timeout may be too short. The recommended config above already sets `UV_HTTP_TIMEOUT=300` (seconds) to avoid this.196197**Session issues:**198199- Browser profile is stored at `~/.linkedin-mcp/profile/`200- Managed browser downloads are cached at `~/.linkedin-mcp/patchright-browsers/`201- Make sure you have only one active LinkedIn session at a time202203**Login issues:**204205- LinkedIn may require a login confirmation in the LinkedIn mobile app for `--login`206- LinkedIn may show a captcha challenge during login. Run `uvx mcp-server-linkedin@latest --login` which opens a browser where you can solve it manually.207208**Timeout issues:**209210- *Page operations failing* (elements not found, navigation hangs): increase the browser page-op timeout — `--timeout 10000` or `TIMEOUT=10000` (milliseconds, default 5000).211- *Entire tool calls timing out* (e.g. multi-section profiles, cold-start Chromium, slow containers): increase the per-tool execution timeout — `--tool-timeout 300` or `TOOL_TIMEOUT=300` (seconds, default 180).212- *First tool call with no session*: if a locally logged-in browser has a live LinkedIn session, the server auto-imports it (see `AUTO_IMPORT_FROM_BROWSER` / `--auto-import`) instead of forcing a manual login. On macOS the keychain may prompt once for Safe Storage access. If no importable browser session exists, it falls back to opening a login window and waits up to `LOGIN_INLINE_WAIT` seconds (default 25, max 45; `--login-inline-wait`) so a quick sign-in resolves in one call. If the wait elapses, the tool returns a pending signal and the model retries in about 30 seconds. Neither the auto-import nor the inline wait applies under Docker or when the server is bound to a non-loopback HTTP host; create the session on the host with `--login`.213- Users on slow connections may need higher values for either.214215**Told to run `--login` on the host when you already did:**216217- If tool calls answer "No valid LinkedIn session is available in Docker" on a machine that is *not* a container, the runtime was misdetected. This happened on Linux hosts running a Docker daemon for unrelated services. Set `LINKEDIN_MCP_CONTAINER=false` to override the detection; `true` forces the opposite.218219**Using a proxy:**220221> **Most people should not use one.** LinkedIn's own guidance for reducing222> security challenges is to avoid a VPN or proxy, and it scores the addresses a223> session signs in from. A home connection you have used for years is a trust224> signal; a commercial exit node with a history you cannot see is not, and225> switching to one is itself the kind of change that triggers a checkpoint.226> A proxy is worth it in one case: the server runs somewhere its address is227> obviously a data centre, or in a different country from the account's history.228> Even then, a WireGuard or Tailscale exit node on your own home network beats229> any paid provider, because the address really is yours. If you do buy one,230> take a dedicated static ISP address and keep it, rather than a rotating231> residential pool.232233- Route the browser through a proxy with `--proxy-server http://host:port` (`http`, `https`, `socks4` and `socks5` are accepted). Only browser traffic is routed, not the MCP transport.234- Credentials go in `PROXY_USERNAME` and `PROXY_PASSWORD`. There is no `--proxy-password` flag on purpose: command-line arguments are readable by every other user on the machine. `PROXY_SERVER` also accepts the combined `http://user:pass@host:port` form most providers hand out.235- Chromium cannot authenticate to a SOCKS proxy, so credentials require an `http(s)` endpoint. If your provider only offers authenticated SOCKS5, run a local relay that holds the credentials and point the server at that.236- Local addresses go through the proxy too. Chromium's usual direct route for `localhost` is removed when a proxy is set, so add `PROXY_BYPASS=localhost,127.0.0.1,::1` if you need local targets reached directly.237- Auto-import is skipped while a proxy is configured: a session taken from a local browser was created on your real address, and moving it to the proxy is the very change that triggers a checkpoint. Use `--login`.238- A wrong proxy password does not report itself: Chromium retries the authentication challenge until the page times out, so it surfaces as a timeout or a failed sign-in. If sessions stop working right after you add a proxy, check the credentials before assuming the session expired.239- **Set the proxy up before creating the session.** Run `--login` with the proxy already configured. Turning a proxy on for an existing profile moves a logged-in session to a new IP, which is what triggers a LinkedIn checkpoint. The same applies to `--import-from-browser`, which imports a session created on your real IP. Use a sticky session, not a rotating pool, for the same reason.240241**Custom Chrome path:**242243- If Chrome is installed in a non-standard location, use `--chrome-path /path/to/chrome`244- Can also set via environment variable: `CHROME_PATH=/path/to/chrome`245246</details>247248<br/>249<br/>250251## 📦 Claude Desktop MCP Bundle (formerly DXT)252253**Prerequisites:** [Claude Desktop](https://claude.ai/download).254255**One-click installation** for Claude Desktop users:2562571. Download the latest `.mcpb` artifact from [releases](https://github.com/stickerdaniel/linkedin-mcp-server/releases/latest)2582. Click the downloaded `.mcpb` file to install it into Claude Desktop2593. Call any LinkedIn tool260261On startup, the MCP Bundle starts preparing the shared Patchright Chromium browser cache in the background. If you call a tool too early, Claude will surface a setup-in-progress error. On the first tool call that needs authentication, the server opens a LinkedIn login browser window and asks you to retry after sign-in.262263### MCP Bundle Setup Help264265<details>266<summary><b>❗ Troubleshooting</b></summary>267268**First-time setup behavior:**269270- Claude Desktop starts the bundle immediately; browser setup continues in the background271- If the Patchright Chromium browser is still downloading, retry the tool after a short wait272- Managed browser downloads are shared under `~/.linkedin-mcp/patchright-browsers/`273274**Login issues:**275276- Make sure you have only one active LinkedIn session at a time277- LinkedIn may require a login confirmation in the LinkedIn mobile app for `--login`278- LinkedIn may show a captcha challenge during login. Run `uvx mcp-server-linkedin@latest --login` which opens a browser where you can solve captchas manually. See the [uvx setup](#-uvx-setup-recommended---universal) for prerequisites.279280**Timeout issues:**281282- *Page operations failing* (elements not found, navigation hangs): increase the browser page-op timeout — `--timeout 10000` or `TIMEOUT=10000` (milliseconds, default 5000).283- *Entire tool calls timing out* (e.g. multi-section profiles, cold-start Chromium, slow containers): increase the per-tool execution timeout — `--tool-timeout 300` or `TOOL_TIMEOUT=300` (seconds, default 180).284- *First tool call with no session*: if a locally logged-in browser has a live LinkedIn session, the server auto-imports it (see `AUTO_IMPORT_FROM_BROWSER` / `--auto-import`) instead of forcing a manual login. On macOS the keychain may prompt once for Safe Storage access. If no importable browser session exists, it falls back to opening a login window and waits up to `LOGIN_INLINE_WAIT` seconds (default 25, max 45; `--login-inline-wait`) so a quick sign-in resolves in one call. If the wait elapses, the tool returns a pending signal and the model retries in about 30 seconds. Neither the auto-import nor the inline wait applies under Docker or when the server is bound to a non-loopback HTTP host; create the session on the host with `--login`.285- Users on slow connections may need higher values for either.286287**Told to run `--login` on the host when you already did:**288289- If tool calls answer "No valid LinkedIn session is available in Docker" on a machine that is *not* a container, the runtime was misdetected. This happened on Linux hosts running a Docker daemon for unrelated services. Set `LINKEDIN_MCP_CONTAINER=false` to override the detection; `true` forces the opposite.290291</details>292293<br/>294<br/>295296## 🐳 Docker Setup297298**Prerequisites:** Make sure you have [Docker](https://www.docker.com/get-started/) installed and running, and [uv](https://docs.astral.sh/uv/getting-started/installation/) installed on the host for the one-time `--login` step.299300### Authentication301302Docker runs headless (no browser window), so you need to create a browser profile locally first and mount it into the container.303304**Step 1: Create profile on the host (one-time setup)**305306```bash307uvx mcp-server-linkedin@latest --login308```309310This opens a browser window where you log in manually (5 minute timeout for 2FA, captcha, etc.). The browser profile and cookies are saved under `~/.linkedin-mcp/`. On startup, Docker derives a Linux browser profile from your host cookies and creates a fresh session each time. If you experience stability issues with Docker, consider using the [uvx setup](#-uvx-setup-recommended---universal) instead.311312**Step 2: Configure Claude Desktop with Docker**313314```json315{316 "mcpServers": {317 "mcp-server-linkedin": {318 "command": "docker",319 "args": [320 "run", "--rm", "-i",321 "-v", "~/.linkedin-mcp:/home/pwuser/.linkedin-mcp",322 "stickerdaniel/linkedin-mcp-server:latest"323 ]324 }325 }326}327```328329> [!NOTE]330> Docker creates a fresh session on each startup. Sessions may expire over time — run `uvx mcp-server-linkedin@latest --login` again if you encounter authentication issues.331332> [!NOTE]333> **Why can't I run `--login` in Docker?** Docker containers don't have a display server. Create a profile on your host using the [uvx setup](#-uvx-setup-recommended---universal) and mount it into Docker.334335### Docker Setup Help336337<details>338<summary><b>🔧 Configuration</b></summary>339340**Transport Modes:**341342- **Default (stdio)**: Standard communication for local MCP servers343- **Streamable HTTP**: For a web-based MCP server344- If no transport is specified, the server defaults to `stdio`345- An interactive terminal without explicit transport shows a chooser prompt346347**CLI Options:**348349- `--log-level {DEBUG,INFO,WARNING,ERROR}` - Set logging level (default: WARNING)350- `--transport {stdio,streamable-http}` - Optional: force transport mode (default: stdio)351- `--host HOST` - HTTP server host (default: 127.0.0.1)352- `--port PORT` - HTTP server port (default: 8000)353- `--path PATH` - HTTP server path (default: /mcp)354- `--logout` - Clear all stored LinkedIn auth state, including source and derived runtime profiles and any retired sessions355- `--timeout MS` - Browser timeout for page operations in milliseconds (default: 5000)356- `--tool-timeout SECONDS` - Per-tool MCP execution timeout in seconds (default: 180.0). Increase further for heavy scrapes / cold-start Chromium / slow networks.357- `--login-timeout SECONDS` - Manual login wait timeout in seconds (default: 1800; 0 = no limit). How long the `--login` browser waits for you to finish signing in.358- `--login-inline-wait SECONDS` - Bounded inline wait for a tool call to resume after login completes, in seconds (default: 25, max 45; 0 = return immediately).359- `--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 when several MCP clients run at the same time.360- `--browser-min-hold SECONDS` - Shortest time this process keeps the shared browser before handing it to a waiting process (default: 20, clamped below `--browser-wait` so a waiting client is served before its own timeout; 0 = hand over after every tool call). Raising it means fewer browser restarts but longer waits for other clients.361- `--browser-idle-timeout SECONDS` - Close an idle browser and release the shared profile after this long without a tool call (default: 600; 0 = keep it open until the server exits).362- `--auto-import` / `--no-auto-import` - Enable or disable auto-import of a session from a locally logged-in browser on the first no-session tool call (before falling back to manual login). Auto-import is on by default across interactive and non-interactive desktop runs; pass `--no-auto-import` (or `AUTO_IMPORT_FROM_BROWSER=false`) to require `--login` / `--import-from-browser` instead. No effect under Docker or on a non-loopback HTTP bind. On macOS the keychain may prompt once for Safe Storage access.363- `--user-data-dir PATH` - Path to persistent browser profile directory (default: ~/.linkedin-mcp/profile)364- `--chrome-path PATH` - Path to Chrome/Chromium executable (rarely needed in Docker)365- `--proxy-server URL` - Route the browser through a proxy, as `scheme://host:port`. Set the password via `PROXY_PASSWORD` (no flag, so it stays out of the process list)366367> [!NOTE]368> `--login` and `--no-headless` are not available in Docker (no display server). Use the [uvx setup](#-uvx-setup-recommended---universal) to create profiles.369370**HTTP Mode Example (for web-based MCP clients):**371372```bash373docker run -it --rm \374 -v ~/.linkedin-mcp:/home/pwuser/.linkedin-mcp \375 -p 8080:8080 \376 stickerdaniel/linkedin-mcp-server:latest \377 --transport streamable-http --host 0.0.0.0 --port 8080 --path /mcp378```379380Runtime server logs are emitted by FastMCP/Uvicorn.381382The HTTP server answers requests addressed to `localhost` or to the address it383is bound to, and refuses others with `421`. That is what stops a website you384merely visit from pointing a domain at this server and using your LinkedIn385session through your own browser.386387Reaching the server by any other name is refused, including a machine name on388your network and the public name in front of a reverse proxy. Either have the389proxy rewrite the upstream `Host` to the backend address, or name the host you390serve it under:391392```bash393FASTMCP_HTTP_ALLOWED_HOSTS='["mcp.example"]'394```395396That permits exactly that name and keeps refusing everything else. The endpoint397still has no authentication, so anything reachable beyond your own machine398belongs behind something that provides it.399400**Test with mcp inspector:**4014021. Install and run mcp inspector ```bunx @modelcontextprotocol/inspector```4032. Click pre-filled token url to open the inspector in your browser4043. Select `Streamable HTTP` as `Transport Type`4054. Set `URL` to `http://localhost:8080/mcp`4065. Connect4076. Test tools408409</details>410411<details>412<summary><b>❗ Troubleshooting</b></summary>413414**Docker issues:**415416- Make sure [Docker](https://www.docker.com/get-started/) is installed417- Check if Docker is running: `docker ps`418419**Login issues:**420421- Make sure you have only one active LinkedIn session at a time422- LinkedIn may require a login confirmation in the LinkedIn mobile app for `--login`423- LinkedIn may show a captcha challenge during login. Run `uvx mcp-server-linkedin@latest --login` which opens a browser where you can solve captchas manually. See the [uvx setup](#-uvx-setup-recommended---universal) for prerequisites.424- If Docker auth becomes stale after you re-login on the host, restart Docker once so it can fresh-bridge from the new source session generation.425426**Timeout issues:**427428- *Page operations failing* (elements not found, navigation hangs): increase the browser page-op timeout — `--timeout 10000` or `TIMEOUT=10000` (milliseconds, default 5000).429- *Entire tool calls timing out* (e.g. multi-section profiles, cold-start Chromium, slow containers): increase the per-tool execution timeout — `--tool-timeout 300` or `TOOL_TIMEOUT=300` (seconds, default 180).430- *First tool call with no session*: if a locally logged-in browser has a live LinkedIn session, the server auto-imports it (see `AUTO_IMPORT_FROM_BROWSER` / `--auto-import`) instead of forcing a manual login. On macOS the keychain may prompt once for Safe Storage access. If no importable browser session exists, it falls back to opening a login window and waits up to `LOGIN_INLINE_WAIT` seconds (default 25, max 45; `--login-inline-wait`) so a quick sign-in resolves in one call. If the wait elapses, the tool returns a pending signal and the model retries in about 30 seconds. Neither the auto-import nor the inline wait applies under Docker or when the server is bound to a non-loopback HTTP host; create the session on the host with `--login`.431- Users on slow connections may need higher values for either.432433**Told to run `--login` on the host when you already did:**434435- If tool calls answer "No valid LinkedIn session is available in Docker" on a machine that is *not* a container, the runtime was misdetected. This happened on Linux hosts running a Docker daemon for unrelated services. Set `LINKEDIN_MCP_CONTAINER=false` to override the detection; `true` forces the opposite.436437**Using a proxy:**438439> **Most people should not use one.** LinkedIn's own guidance for reducing440> security challenges is to avoid a VPN or proxy, and it scores the addresses a441> session signs in from. A home connection you have used for years is a trust442> signal; a commercial exit node with a history you cannot see is not, and443> switching to one is itself the kind of change that triggers a checkpoint.444> A proxy is worth it in one case: the server runs somewhere its address is445> obviously a data centre, or in a different country from the account's history.446> Even then, a WireGuard or Tailscale exit node on your own home network beats447> any paid provider, because the address really is yours. If you do buy one,448> take a dedicated static ISP address and keep it, rather than a rotating449> residential pool.450451- Route the browser through a proxy with `--proxy-server http://host:port` (`http`, `https`, `socks4` and `socks5` are accepted). Only browser traffic is routed, not the MCP transport.452- Credentials go in `PROXY_USERNAME` and `PROXY_PASSWORD`. There is no `--proxy-password` flag on purpose: command-line arguments are readable by every other user on the machine. `PROXY_SERVER` also accepts the combined `http://user:pass@host:port` form most providers hand out.453- Chromium cannot authenticate to a SOCKS proxy, so credentials require an `http(s)` endpoint. If your provider only offers authenticated SOCKS5, run a local relay that holds the credentials and point the server at that.454- Local addresses go through the proxy too. Chromium's usual direct route for `localhost` is removed when a proxy is set, so add `PROXY_BYPASS=localhost,127.0.0.1,::1` if you need local targets reached directly.455- Auto-import is skipped while a proxy is configured: a session taken from a local browser was created on your real address, and moving it to the proxy is the very change that triggers a checkpoint. Use `--login`.456- A wrong proxy password does not report itself: Chromium retries the authentication challenge until the page times out, so it surfaces as a timeout or a failed sign-in. If sessions stop working right after you add a proxy, check the credentials before assuming the session expired.457- **Set the proxy up before creating the session.** Run `--login` with the proxy already configured. Turning a proxy on for an existing profile moves a logged-in session to a new IP, which is what triggers a LinkedIn checkpoint. The same applies to `--import-from-browser`, which imports a session created on your real IP. Use a sticky session, not a rotating pool, for the same reason.458459**Custom Chrome path:**460461- If Chrome is installed in a non-standard location, use `--chrome-path /path/to/chrome`462- Can also set via environment variable: `CHROME_PATH=/path/to/chrome`463464</details>465466<br/>467<br/>468469## 🐍 Local Setup (Develop & Contribute)470471Contributions are welcome! See [CONTRIBUTING.md](CONTRIBUTING.md) for architecture guidelines and checklists. Please [open an issue](https://github.com/stickerdaniel/linkedin-mcp-server/issues) first to discuss the feature or bug fix before submitting a PR.472473**Prerequisites:** [Git](https://git-scm.com/downloads) and [uv](https://docs.astral.sh/uv/) installed474475### Installation476477```bash478# 1. Clone repository479git clone https://github.com/stickerdaniel/linkedin-mcp-server480cd linkedin-mcp-server481482# 2. Install UV package manager (if not already installed)483curl -LsSf https://astral.sh/uv/install.sh | sh484485# 3. Install dependencies486uv sync487uv sync --group dev488489# 4. Install pre-commit hooks490uv run pre-commit install491492# 5. Start the server493uv run -m linkedin_mcp_server494```495496The local server uses the same managed-runtime flow as MCPB and `uvx`: it prepares the Patchright Chromium browser cache in the background and opens LinkedIn login on the first auth-requiring tool call. You can still run `uv run -m linkedin_mcp_server --login` when you want to create the session explicitly.497498### Local Setup Help499500<details>501<summary><b>🔧 Configuration</b></summary>502503**CLI Options:**504505- `--login` - Open browser to log in and save persistent profile506- `--import-from-browser [BROWSER]` - Import a LinkedIn session from a locally logged-in Chromium browser (`chrome`, `chromium`, `brave`, `edge`, `arc`, `vivaldi`, `helium`, `yandex`, `whale`, or `auto`). Bare flag picks `auto`, which auto-selects the most recently used browser with a live LinkedIn session.507- `--no-headless` - Show browser window (useful for debugging scraping issues)508- `--log-level {DEBUG,INFO,WARNING,ERROR}` - Set logging level (default: WARNING)509- `--transport {stdio,streamable-http}` - Optional: force transport mode (default: stdio)510- `--host HOST` - HTTP server host (default: 127.0.0.1)511- `--port PORT` - HTTP server port (default: 8000)512- `--path PATH` - HTTP server path (default: /mcp)513- `--logout` - Clear stored LinkedIn browser profile514- `--timeout MS` - Browser timeout for page operations in milliseconds (default: 5000)515- `--tool-timeout SECONDS` - Per-tool MCP execution timeout in seconds (default: 180.0). Increase further for heavy scrapes / cold-start Chromium / slow networks.516- `--status` - Check if current session is valid and exit517- `--user-data-dir PATH` - Path to persistent browser profile directory (default: ~/.linkedin-mcp/profile)518- `--slow-mo MS` - Delay between browser actions in milliseconds (default: 0, useful for debugging)519- `--user-agent STRING` - Custom browser user agent520- `--viewport WxH` - Browser viewport size (default: 1280x720)521- `--chrome-path PATH` - Path to Chrome/Chromium executable (for custom browser installations)522- `--proxy-server URL` - Route the browser through a proxy, as `scheme://host:port`. Set the password via `PROXY_PASSWORD` (no flag, so it stays out of the process list)523- `--help` - Show help524525> **Note:** Most CLI options have environment variable equivalents. See `.env.example` for details.526527**HTTP Mode Example (for web-based MCP clients):**528529```bash530uv run -m linkedin_mcp_server --transport streamable-http --host 127.0.0.1 --port 8000 --path /mcp531```532533**Claude Desktop:**534535```json536{537 "mcpServers": {538 "mcp-server-linkedin": {539 "command": "uv",540 "args": ["--directory", "/path/to/linkedin-mcp-server", "run", "-m", "linkedin_mcp_server"]541 }542 }543}544```545546`stdio` is used by default for this config.547548</details>549550<details>551<summary><b>❗ Troubleshooting</b></summary>552553**Login issues:**554555- Make sure you have only one active LinkedIn session at a time556- LinkedIn may require a login confirmation in the LinkedIn mobile app for `--login`557- LinkedIn may show a captcha challenge during login. The `--login` command opens a browser where you can solve it manually.558559**Scraping issues:**560561- Use `--no-headless` to see browser actions and debug scraping problems562- Add `--log-level DEBUG` to see more detailed logging563564**Session issues:**565566- Browser profile is stored at `~/.linkedin-mcp/profile/`567- Use `--logout` to clear the profile and start fresh568569**Python/Patchright issues:**570571- Check Python version: `python --version` (should be 3.12+)572- Reinstall Patchright: `uv run patchright install chromium`573- Reinstall dependencies: `uv sync --reinstall`574575**Timeout issues:**576577- *Page operations failing* (elements not found, navigation hangs): increase the browser page-op timeout — `--timeout 10000` or `TIMEOUT=10000` (milliseconds, default 5000).578- *Entire tool calls timing out* (e.g. multi-section profiles, cold-start Chromium, slow containers): increase the per-tool execution timeout — `--tool-timeout 300` or `TOOL_TIMEOUT=300` (seconds, default 180).579- *First tool call with no session*: if a locally logged-in browser has a live LinkedIn session, the server auto-imports it (see `AUTO_IMPORT_FROM_BROWSER` / `--auto-import`) instead of forcing a manual login. On macOS the keychain may prompt once for Safe Storage access. If no importable browser session exists, it falls back to opening a login window and waits up to `LOGIN_INLINE_WAIT` seconds (default 25, max 45; `--login-inline-wait`) so a quick sign-in resolves in one call. If the wait elapses, the tool returns a pending signal and the model retries in about 30 seconds. Neither the auto-import nor the inline wait applies under Docker or when the server is bound to a non-loopback HTTP host; create the session on the host with `--login`.580- Users on slow connections may need higher values for either.581582**Told to run `--login` on the host when you already did:**583584- If tool calls answer "No valid LinkedIn session is available in Docker" on a machine that is *not* a container, the runtime was misdetected. This happened on Linux hosts running a Docker daemon for unrelated services. Set `LINKEDIN_MCP_CONTAINER=false` to override the detection; `true` forces the opposite.585586**Using a proxy:**587588> **Most people should not use one.** LinkedIn's own guidance for reducing589> security challenges is to avoid a VPN or proxy, and it scores the addresses a590> session signs in from. A home connection you have used for years is a trust591> signal; a commercial exit node with a history you cannot see is not, and592> switching to one is itself the kind of change that triggers a checkpoint.593> A proxy is worth it in one case: the server runs somewhere its address is594> obviously a data centre, or in a different country from the account's history.595> Even then, a WireGuard or Tailscale exit node on your own home network beats596> any paid provider, because the address really is yours. If you do buy one,597> take a dedicated static ISP address and keep it, rather than a rotating598> residential pool.599600- Route the browser through a proxy with `--proxy-server http://host:port` (`http`, `https`, `socks4` and `socks5` are accepted). Only browser traffic is routed, not the MCP transport.601- Credentials go in `PROXY_USERNAME` and `PROXY_PASSWORD`. There is no `--proxy-password` flag on purpose: command-line arguments are readable by every other user on the machine. `PROXY_SERVER` also accepts the combined `http://user:pass@host:port` form most providers hand out.602- Chromium cannot authenticate to a SOCKS proxy, so credentials require an `http(s)` endpoint. If your provider only offers authenticated SOCKS5, run a local relay that holds the credentials and point the server at that.603- Local addresses go through the proxy too. Chromium's usual direct route for `localhost` is removed when a proxy is set, so add `PROXY_BYPASS=localhost,127.0.0.1,::1` if you need local targets reached directly.604- Auto-import is skipped while a proxy is configured: a session taken from a local browser was created on your real address, and moving it to the proxy is the very change that triggers a checkpoint. Use `--login`.605- A wrong proxy password does not report itself: Chromium retries the authentication challenge until the page times out, so it surfaces as a timeout or a failed sign-in. If sessions stop working right after you add a proxy, check the credentials before assuming the session expired.606- **Set the proxy up before creating the session.** Run `--login` with the proxy already configured. Turning a proxy on for an existing profile moves a logged-in session to a new IP, which is what triggers a LinkedIn checkpoint. The same applies to `--import-from-browser`, which imports a session created on your real IP. Use a sticky session, not a rotating pool, for the same reason.607608**Custom Chrome path:**609610- If Chrome is installed in a non-standard location, use `--chrome-path /path/to/chrome`611- Can also set via environment variable: `CHROME_PATH=/path/to/chrome`612613</details>614615616<br/>617<br/>618619> [!IMPORTANT]620> **FAQ**621>622> **Is this safe to use? Will I get banned?**623> 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](https://github.com/stickerdaniel/linkedin-mcp-server/discussions).624>625> **What if my agents execute too many actions?**626> 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.627628## Acknowledgements629630Built with [FastMCP](https://gofastmcp.com/) and [Patchright](https://github.com/Kaliiiiiiiiii-Vinyzu/patchright-python).631632Use in accordance with [LinkedIn's User Agreement](https://www.linkedin.com/legal/user-agreement). Automated access may violate LinkedIn's terms and can lead to account restrictions. This tool is for personal use only and comes with no warranty of any kind.633634## License635636This project is licensed under the Apache 2.0 license.637638<br>639
Full transparency — inspect the skill content before installing.