linkedin-mcp-server MCP工具

3. Install dependencies

uv sync uv sync --group dev

Installation Methods - LinkedIn MCP Server

<br/> <br/>

Setup with uvx (Recommended)

Prerequisites: Install uv.

Installation

Add to your MCP client's mcpServers 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 and prepares the shared Patchright Chromium browser cache in the background under ~/.linkedin-mcp/patchright-browsers. On the first tool call that needs authentication, it reuses a LinkedIn session from a signed-in local browser if it finds one, and otherwise opens a LinkedIn login browser window.

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, coccoc, opera, opera_gx, 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 calls that read many pages, 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, Naver Whale, Cốc Cốc, Opera, or Opera GX, you can skip the manual --login step and reuse that session:

```bash

Installation

1. Download the latest .mcpb artifact from releases
2. Click the downloaded .mcpb file to install it into Claude Desktop
3. Call any LinkedIn tool

On startup, the MCP Bundle prepares the shared Patchright Chromium browser cache in the background. On the first tool call that needs authentication, the server reuses a LinkedIn session from a signed-in local browser if it finds one, and otherwise opens a LinkedIn login browser window.

[!NOTE] Early tool calls may return a setup/authentication-in-progress error until browser setup or login finishes. Retry the tool call once the browser download or sign-in completes.

Setup Help

<details> <summary><b>❗ Troubleshooting</b></summary>

<details> <summary>First-time setup behavior</summary>

• Claude Desktop starts the bundle immediately; browser setup continues in the background
• If the Patchright Chromium browser is still downloading, retry the tool after a short wait
• Managed browser downloads are shared under ~/.linkedin-mcp/patchright-browsers/
• The browser cache keeps growing: Patchright keeps an old Chromium revision for as long as any installed version still references it, so an upgrade can leave both on disk. The server logs a warning naming what it holds. To reclaim the space, stop every LinkedIn MCP Server instance, delete ~/.linkedin-mcp/patchright-browsers/, and let the next launch download the current browser.
• Windows, the bundle exits with DLL load failed while importing _greenlet: install the Microsoft Visual C++ Redistributable, or reinstall a bundle pinning greenlet 3.5.5 or newer, whose published Windows wheels carry the C++ runtime inside the extension again. A bundle pinning greenlet 3.3.1 through 3.5.4 needs MSVCP140.dll from that redistributable, which neither the python.org installer nor the uv-managed builds carry, and a greenlet built from source can need it at any version. The server names this itself on startup, and only after checking that the loader cannot produce that DLL. Reported as greenlet#525, fixed in greenlet#526.

</details>

<details> <summary>Login issues</summary>

• Make sure you have only one active LinkedIn session at a time
• LinkedIn may require a login confirmation in the LinkedIn mobile app for --login
• 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 for prerequisites.

</details>

<details> <summary>Timeout issues</summary>

• Page operations failing (elements not found, navigation hangs): increase the browser page-op timeout: --timeout 10000 or TIMEOUT=10000 (milliseconds, default 5000).
• 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).
• 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, or use the explicit Docker --login --login-viewer command.
• Users on slow connections may need higher values for either.

</details>

<details> <summary>Told to run <code>--login</code> on the host when you already did</summary>

• 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.

</details>

</details>

<br/> <br/>

Installation

Run in a terminal

codex plugin marketplace add stickerdaniel/linkedin-mcp-server
codex plugin add linkedin-mcp-server@linkedin-mcp-server

The plugin runs the latest server release. On the first tool call that needs authentication, the server reuses a LinkedIn session from a signed-in local browser or opens a login window.

[!NOTE] Early tool calls may return a setup/authentication-in-progress error until browser setup or login finishes. Retry the tool call once the browser download or sign-in completes.

<br/> <br/>

Installation

Run in a terminal

claude plugin marketplace add stickerdaniel/linkedin-mcp-server
claude plugin install linkedin-mcp-server@linkedin-mcp-server

The plugin runs the latest server release. On the first tool call that needs authentication, the server reuses a LinkedIn session from a signed-in local browser or opens a login window.

[!NOTE] Early tool calls may return a setup/authentication-in-progress error until browser setup or login finishes. Retry the tool call once the browser download or sign-in completes.

<br/> <br/>

Installation

From the Cursor Marketplace: open Customize in the sidebar, search for LinkedIn MCP, and choose Install. The plugin bundles the LinkedIn skill.

One-click MCP install (server only, without the skill):

Both run the latest server release. On the first tool call that needs authentication, the server reuses a LinkedIn session from a signed-in local browser or opens a login window.

[!NOTE] Early tool calls may return a setup/authentication-in-progress error until browser setup or login finishes. Retry the tool call once the browser download or sign-in completes.

<br/> <br/>

Setup with Docker

<details> <summary><strong>I know what I'm doing</strong></summary>

Prerequisites: Make sure Docker is installed and running.

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:

• --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 (ignored in Docker). On macOS the keychain may prompt once.
• --logout - Clear the stored session and every profile derived from it
• --login-viewer - With --login, show the login browser at a token-protected URL on port 6080. Needs the profile mount from 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 calls that read many pages, 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:

• --chrome-path PATH - Path to a Chrome/Chromium executable (rarely needed in Docker)
• --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)

[!NOTE] Plain --login still has no visible window in Docker. Add --login-viewer and publish 127.0.0.1:6080:6080 only for the one-shot login command. Docker is already headed by default, so --no-headless changes nothing. The experimental --daemon is ignored in Docker because its owner can outlive the virtual display.

</details>

<details> <summary>HTTP mode</summary>

HTTP Mode Example (for web-based MCP clients):

Bash / macOS / Linux:

docker run -it --rm \
  -v ~/.linkedin-mcp:/home/pwuser/.linkedin-mcp \
  -p 127.0.0.1:8080:8080 \
  stickerdaniel/linkedin-mcp-server:latest \
  --transport streamable-http --host 0.0.0.0 --port 8080 --path /mcp

PowerShell (Windows):

$sessionDir = Join-Path $env:USERPROFILE ".linkedin-mcp"
docker run -it --rm `
  -v "${sessionDir}:/home/pwuser/.linkedin-mcp" `
  -p 127.0.0.1:8080:8080 `
  stickerdaniel/linkedin-mcp-server:latest `
  --transport streamable-http --host 0.0.0.0 --port 8080 --path /mcp

Both halves of that are needed, and they do different jobs. --host 0.0.0.0 makes the server reachable inside the container: a process bound to 127.0.0.1 in there cannot be reached through a published port at all. The 127.0.0.1: in front of -p is what limits it outside, to this machine. Drop that prefix and Docker publishes on every interface, which puts an endpoint with no authentication on your network. The server cannot tell the two apart, so it warns either way.

Loopback publishing limits this to the machine, not to the container. Other containers on the same host can still reach it through host.docker.internal wherever that name resolves, which is the default on Docker Desktop and OrbStack but not on native Linux Docker.

Runtime server logs are emitted by FastMCP/Uvicorn.

The HTTP server answers requests addressed to localhost or to the address it is bound to, and refuses others with 421. That is what stops a website you merely visit from pointing a domain at this server and using your LinkedIn session through your own browser.

Reaching the server by any other name is refused, including a machine name on your network and the public name in front of a reverse proxy. Either have the proxy rewrite the upstream Host to the backend address, or name the host you serve it under:

FASTMCP_HTTP_ALLOWED_HOSTS='["mcp.example"]'

That permits exactly that name and keeps refusing everything else. The endpoint still has no authentication, so anything reachable beyond your own machine belongs behind something that provides it.

Test with mcp inspector:

1. Install and run mcp inspector

    @modelcontextprotocol/inspector

2. Click pre-filled token url to open the inspector in your browser
3. Select Streamable HTTP as Transport Type
4. Set URL to http://localhost:8080/mcp
5. Connect
6. Test tools

</details>

</details>

<details> <summary><b>❗ Troubleshooting</b></summary>

<details> <summary>Docker issues</summary>

• Make sure Docker is installed
• Check if Docker is running: docker ps
• Permission errors on ~/.linkedin-mcp: an older rootful Docker run may have created the directory as root. Fix it with sudo chown -R "$(id -u):$(id -g)" ~/.linkedin-mcp.

</details>

<details> <summary>Login issues</summary>

• Make sure you have only one active LinkedIn session at a time
• LinkedIn may require a login confirmation in the LinkedIn mobile app for --login
• 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 for prerequisites.
• 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.

</details>

<details> <summary>Timeout issues</summary>

• Page operations failing (elements not found, navigation hangs): increase the browser page-op timeout: --timeout 10000 or TIMEOUT=10000 (milliseconds, default 5000).
• 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).
• 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, or use the explicit Docker --login --login-viewer command.
• Users on slow connections may need higher values for either.

</details>

<details> <summary>Told to run <code>--login</code> on the host when you already did</summary>

• 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.

</details>

<details> <summary>Custom Chrome path</summary>

• If Chrome is installed in a non-standard location, use --chrome-path /path/to/chrome
• Can also set via environment variable: CHROME_PATH=/path/to/chrome
• On macOS and Linux the browser must be at least as new as the one that last opened your profile, and the server refuses the launch otherwise. (Not on Windows: a browser there cannot be asked its version without starting one, so the check is off.) An older browser can silently drop stores a newer one wrote, the saved session among them, and the failure then looks exactly like an expired login. The message names both versions. Going back to the bundled Chromium after running a newer Chrome once is the usual way to meet this; either run the newer browser again, whichever one that was, or run --login, which moves the stored session aside and signs in fresh with the browser you have. --logout also clears it but discards the old session instead of keeping it recoverable, and it asks for confirmation on the terminal, so it is not usable from a server an MCP client started.
• Only Chrome, Chromium and Chrome for Testing are compared this way. Forks number themselves differently (Vivaldi is on 7.x, Edge's build number sits far below Chrome's under the same major), so pointing CHROME_PATH at one turns the check off rather than producing a refusal nothing could satisfy.
• In the documented Docker setup this check does not apply. The container never opens the profile you created with --login; it derives its own from your cookies, and by default rebuilds that from scratch on every start, so there is nothing for an older image to downgrade. With EXPERIMENTAL_PERSIST_DERIVED_RUNTIME the derived profile is kept, and an image tag that moves backwards then throws it away and re-derives it, again with nothing for you to do. The check matters on the host, where the server opens that profile directly. Not during --login itself, which moves the old profile aside before it starts a browser and so can never trip it.

</details>

</details>

</details>

<br/> <br/>

Setup Help

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

• Set the proxy up before --login. Moving an existing session to a new address triggers a LinkedIn checkpoint. That includes a session from --import-from-browser, which was created on your real address.
• --proxy-server scheme://host:port or PROXY_SERVER, with http, https, socks4 or socks5. Only browser traffic is routed, not the MCP transport.
• Pass credentials through PROXY_USERNAME and PROXY_PASSWORD, or include them in PROXY_SERVER using the combined http://user:pass@host:port form. The combined form is not accepted by the --proxy-server CLI option.
• PROXY_BYPASS=localhost,127.0.0.1,::1 reaches local targets directly. With a proxy set, Chromium routes localhost through it too.

</details>

<details> <summary><b>❗ Troubleshooting</b></summary>

• 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.
• A wrong proxy password shows up as a timeout or a failed sign-in, because Chromium retries the authentication challenge until the page times out. If sessions stop working right after you add a proxy, check the proxy credentials first.
• Auto-import is skipped while a proxy is configured: the imported session would move from your real address to the proxy. Use --login.
• Inside a container 127.0.0.1 is the container itself, so a relay on the host is host.docker.internal; native Linux Docker also needs --add-host=host.docker.internal:host-gateway.

</details>

<br/> <br/>

Setup from Source (Develop & Contribute)

Contributions are welcome. See CONTRIBUTING.md for architecture guidelines and checklists. Search existing issues first, then use the issue forms for anything new. AI agents follow the issue-packet skill.

Prerequisites: Git and uv installed

Installation

Run in a terminal

```bash

2. Install UV package manager (if not already installed)

curl -LsSf https://astral.sh/uv/install.sh | sh

4. Install pre-commit hooks

uv run pre-commit install

Setup Help

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

<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, coccoc, opera, opera_gx, 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.
• --status - Check whether the stored session is valid, then exit
• --logout - Clear the stored session
• --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 calls that read many pages, 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)
• --slow-mo MS - Delay between browser actions (default: 0, useful for debugging)
• --viewport WxH - Viewport size (default: 1280x720). Applies to windowless mode only; a headed launch uses the real window size.
• --chrome-path PATH - Path to a Chrome/Chromium executable
• --installer-temp-dir PATH - Existing directory for browser installation temporary files (environment: INSTALLER_TEMP_DIR).
• --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)
• --help - Show help

Note: Most CLI options have environment variable equivalents. See .env.example for details.

</details>

<details> <summary>HTTP mode and Claude Desktop</summary>

HTTP Mode Example (for web-based MCP clients):

uv run -m linkedin_mcp_server --transport streamable-http --host 127.0.0.1 --port 8000 --path /mcp

Claude Desktop:

{
  "mcpServers": {
    "mcp-server-linkedin": {
      "command": "uv",
      "args": ["--directory", "/path/to/linkedin-mcp-server", "run", "-m", "linkedin_mcp_server"]
    }
  }
}

stdio is used by default for this config.

</details>

</details>

<details> <summary><b>❗ Troubleshooting</b></summary>

<details> <summary>Login issues</summary>

• Make sure you have only one active LinkedIn session at a time
• LinkedIn may require a login confirmation in the LinkedIn mobile app for --login
• LinkedIn may show a captcha challenge during login. The --login command opens a browser where you can solve it manually.

</details>

<details> <summary>Tool issues</summary>

• Use --no-headless to watch the browser when a tool returns wrong or missing data
• Add --log-level DEBUG to see more detailed logging

</details>

<details> <summary>Session issues</summary>

• Browser profile is stored at ~/.linkedin-mcp/profile/
• Managed browser downloads are cached at ~/.linkedin-mcp/patchright-browsers/, shared with the uvx and MCP Bundle installations
• The browser cache keeps growing: Patchright keeps an old Chromium revision for as long as any installed version still references it, and a uv archive or a second worktree is such a reference. The server logs a warning naming what it holds. To reclaim the space, stop every LinkedIn MCP Server instance, delete ~/.linkedin-mcp/patchright-browsers/, and let the next launch download the current browser.
• Use --logout to clear the profile and start fresh

</details>

<details> <summary>Python/Patchright issues</summary>

• Check Python version: python --version (should be 3.12.4+)
• Reinstall Patchright: uv run patchright install chromium
• Reinstall dependencies: uv sync --reinstall

</details>

<details> <summary>Timeout issues</summary>

• Page operations failing (elements not found, navigation hangs): increase the browser page-op timeout: --timeout 10000 or TIMEOUT=10000 (milliseconds, default 5000).
• 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).
• 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, or use the explicit Docker --login --login-viewer command.
• Users on slow connections may need higher values for either.

</details>

<details> <summary>Told to run <code>--login</code> on the host when you already did</summary>

• 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.

</details>

<details> <summary>Custom Chrome path</summary>

• If Chrome is installed in a non-standard location, use --chrome-path /path/to/chrome
• Can also set via environment variable: CHROME_PATH=/path/to/chrome
• On macOS and Linux the browser must be at least as new as the one that last opened your profile, and the server refuses the launch otherwise. (Not on Windows: a browser there cannot be asked its version without starting one, so the check is off.) An older browser can silently drop stores a newer one wrote, the saved session among them, and the failure then looks exactly like an expired login. The message names both versions. Going back to the bundled Chromium after running a newer Chrome once is the usual way to meet this; either run the newer browser again, whichever one that was, or run --login, which moves the stored session aside and signs in fresh with the browser you have. --logout also clears it but discards the old session instead of keeping it recoverable, and it asks for confirmation on the terminal, so it is not usable from a server an MCP client started.
• Only Chrome, Chromium and Chrome for Testing are compared this way. Forks number themselves differently (Vivaldi is on 7.x, Edge's build number sits far below Chrome's under the same major), so pointing CHROME_PATH at one turns the check off rather than producing a refusal nothing could satisfy.

</details>

</details>

<br/> <br/>

[!IMPORTANT] FAQ Is this safe to use? Will I get banned? 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. What if my agents execute too many actions? 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.

Codex Plugin

Prerequisites: Codex and uv.

Claude Code Plugin

Prerequisites: Claude Code and uv.

Cursor Plugin

Prerequisites: Cursor and uv on your PATH.