LinkedIn MCP Server

To use the LinkedIn MCP server in a Docker container, you must first create a browser profile on your host machine to handle authentication. Docker containers cannot open a browser window for manual login.

Step 1: Create a profile on your host

You need uv installed on your host. Run the following command to open a browser window and log in to LinkedIn manually. The session will be saved to ~/.linkedin-mcp/.

uvx mcp-server-linkedin@latest --login

Alternative: Import an existing session If you are already logged into LinkedIn in a local browser (Chrome, Brave, Edge, etc.), you can reuse that session instead of performing a new login:

uvx mcp-server-linkedin@latest --import-from-browser

Note: This does not work for Chrome 127+ if app-bound encryption is used. In that case, use --login.

Step 2: Configure Claude Desktop

{
  "mcpServers": {
    "mcp-server-linkedin": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-v", "~/.linkedin-mcp:/home/pwuser/.linkedin-mcp",
        "stickerdaniel/linkedin-mcp-server:latest"
      ]
    }
  }
}

To develop or contribute to the project, follow these steps to clone the repository and install dependencies using uv.

Prerequisites:

• Git
• uv

Steps:

1. Clone the repository and enter the directory.
2. Install the uv package manager.
3. Synchronize dependencies for both the main project and development group.
4. Install pre-commit hooks.
5. Start the server using the module flag.

Note: The local server manages the Patchright Chromium browser cache automatically. You can explicitly create a session by running the server with the --login flag.

# 1. Clone repository
git clone https://github.com/stickerdaniel/linkedin-mcp-server
cd linkedin-mcp-server

# 2. Install UV package manager (if not already installed)
curl -LsSf https://astral.sh/uv/install.sh | sh

# 3. Install dependencies
uv sync
uv sync --group dev

# 4. Install pre-commit hooks
uv run pre-commit install

# 5. Start the server
uv run -m linkedin_mcp_server

To run the LinkedIn MCP server in Docker, you must first create a browser profile on your host machine because Docker runs headless and cannot open a browser window for manual login.

1. Create a profile on the host: Run uvx mcp-server-linkedin@latest --login. This opens a browser for manual login. Profiles are saved to ~/.linkedin-mcp/.
2. Configure Claude Desktop: Add the Docker configuration to your mcpServers settings, mounting the host profile directory into the container.

Note: Docker creates a fresh session on each startup. If authentication fails, re-run the --login command on your host.

# Step 1: Create profile on host
uvx mcp-server-linkedin@latest --login

// Step 2: Claude Desktop Configuration
{
  "mcpServers": {
    "mcp-server-linkedin": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-v", "~/.linkedin-mcp:/home/pwuser/.linkedin-mcp",
        "stickerdaniel/linkedin-mcp-server:latest"
      ]
    }
  }
}

The server requires a LinkedIn session to function. You can establish a session in two ways:

1. Manual Login (Recommended for new setups): Run the following command to open a browser window where you can sign in manually and solve any CAPTCHAs: uvx mcp-server-linkedin@latest --login

2. Import from an existing browser session: If you are already logged into LinkedIn in a local browser (Chrome, Brave, Edge, etc.), you can import that session to skip manual login:

   • Auto-pick the most recent session: uvx mcp-server-linkedin@latest --import-from-browser
   • Target a specific browser: uvx mcp-server-linkedin@latest --import-from-browser <browser_name> (e.g., brave, edge, chrome).

Important: If you use a proxy, configure it before running --login or --import-from-browser to avoid triggering LinkedIn security checkpoints.

uvx mcp-server-linkedin@latest --login
# OR
uvx mcp-server-linkedin@latest --import-from-browser brave

Login & Session Issues

• Manual Login: If automated login fails, use the --login command to open a browser window where you can manually solve captchas or handle mobile app confirmations.
• Clearing Sessions: If your session is corrupted, use --logout to clear the profile stored at ~/.linkedin-mcp/profile/.
• Docker Detection: If running on a non-containerized Linux host and receiving "No valid LinkedIn session is available in Docker" errors, set the environment variable LINKEDIN_MCP_CONTAINER=false.

Scraping & Timeout Issues

• Debugging Scraping: Use --no-headless to watch the browser actions and --log-level DEBUG for detailed logs.
• Page Operation Timeouts: If elements aren't being found or navigation hangs, increase the page timeout using --timeout 10000 (milliseconds).
• Tool Execution Timeouts: For heavy scrapes or slow networks, increase the per-tool timeout using --tool-timeout 300 (seconds).

Proxy Configuration

• Setup Order: Always set up your proxy before creating a session. Run --login with the proxy already configured. Switching to a proxy with an existing profile will likely trigger a LinkedIn security checkpoint.
• Authentication: Use PROXY_USERNAME and PROXY_PASSWORD environment variables. Chromium does not support SOCKS proxy authentication; use an http(s) endpoint.
• Localhost Access: If using a proxy, you may need to set PROXY_BYPASS=localhost,127.0.0.1,::1 to ensure local targets are reached directly.