stickerdaniel/linkedin-mcp-server repository overview

⁠MCP Server for LinkedIn

A Model Context Protocol (MCP) server that connects AI assistants to LinkedIn. Access profiles, companies, and job postings through a Docker container.

⁠Features

• Profile Access: Get detailed LinkedIn profile information including experience, education, skills, projects, certifications, and more
• Own Profile: Fetch the authenticated user's own profile to give agents self-context
• Profile Connections: Send connection requests or accept incoming ones, with optional notes
• Sidebar Profiles: Extract profile URLs from the sidebar recommendation sections on a profile page ("More profiles for you", "Explore premium profiles", "People you may know")
• Messaging: List the inbox, read a conversation by username or thread ID, search messages by keyword, and compose/send a new message with explicit confirmation (profile-based send may open a separate DM rather than reply in an existing thread)
• Company Profiles: Extract comprehensive company data, including the LinkedIn company URN id (used by LinkedIn's people-search currentCompany URL facet)
• Company Employees: List employees at a company with optional keyword filtering
• Company Search: Search for companies by keyword
• Job Details: Retrieve job posting information
• Job Search: Search for jobs with keywords and location filters
• Saved Jobs: List job postings saved by the authenticated user
• People Search: Search for people by keywords and location
• Person Posts: Get recent activity/posts from a person's profile
• Company Posts: Get recent posts from a company's LinkedIn feed
• Home Feed: Get recent posts from the authenticated user's LinkedIn home feed
• Post Search: Search posts/content globally by keyword (the "Posts" tab) with an optional recency filter
• Compact References: Return typed per-section links alongside readable text without shipping full-page markdown

⁠Quick Start

The image ships full Chromium. Log in once through a browser the container shows you in your own browser tab.

macOS / Linux:

# Create the directory first so the container can save your session into it
mkdir -p ~/.linkedin-mcp
docker run -it --rm \
  -v ~/.linkedin-mcp:/home/pwuser/.linkedin-mcp \
  -p 127.0.0.1:6080:6080 \
  stickerdaniel/linkedin-mcp-server:latest \
  --login --login-viewer

PowerShell (Windows):

$sessionDir = Join-Path $env:USERPROFILE ".linkedin-mcp"
New-Item -ItemType Directory -Force -Path $sessionDir | Out-Null
docker run -it --rm `
  -v "${sessionDir}:/home/pwuser/.linkedin-mcp" `
  -p 127.0.0.1:6080:6080 `
  stickerdaniel/linkedin-mcp-server:latest `
  --login --login-viewer

Open the full URL the command prints (it carries the access token) and sign in. The viewer closes itself afterwards; let the command exit on its own so the session is stored completely. It gives up after 30 minutes.

Keep the same host directory mounted at /home/pwuser/.linkedin-mcp on every later docker run. A session created on the host with uvx mcp-server-linkedin@latest --login works too, and the container then rebuilds its own profile from those cookies on each start.

If an older rootful Docker run left that host directory owned by root, repair it with sudo chown -R "$(id -u):$(id -g)" ~/.linkedin-mcp.

Configure Claude Desktop with Docker

macOS / Linux (absolute path in JSON):

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

Spell that first path out in full. A client runs docker directly rather than through a shell, so a leading ~ reaches Docker unexpanded and it refuses the mount.

PowerShell (Windows): use a forward-slash JSON path. A backslash path like C:\Users\Alice\.linkedin-mcp fails JSON parsing because \U is an invalid escape. Replace Alice with your username.

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

Use $env:USERPROFILE\.linkedin-mcp when constructing the host path outside JSON.

⁠Environment Variables

Example with custom timeouts (macOS / Linux):

{
  "mcpServers": {
    "mcp-server-linkedin": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-v", "/absolute/path/to/.linkedin-mcp:/home/pwuser/.linkedin-mcp",
        "-e", "TIMEOUT=10000",
        "-e", "TOOL_TIMEOUT=300",
        "stickerdaniel/linkedin-mcp-server"
      ]
    }
  }
}

Example with custom timeouts (Windows):

{
  "mcpServers": {
    "mcp-server-linkedin": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-v", "C:/Users/Alice/.linkedin-mcp:/home/pwuser/.linkedin-mcp",
        "-e", "TIMEOUT=10000",
        "-e", "TOOL_TIMEOUT=300",
        "stickerdaniel/linkedin-mcp-server"
      ]
    }
  }
}

⁠Repository

• Source: https://github.com/stickerdaniel/linkedin-mcp-server⁠
• License: Apache 2.0