icon for mcp server

LinkedIn

STDIO

LinkedIn MCP server for scraping profiles, companies, and jobs through AI assistants.

LinkedIn MCP Server

CI Status Release License

Through this LinkedIn MCP server, AI assistants like Claude can connect to your LinkedIn. Give access to profiles and companies, get your recommended jobs, or search for keywords. All from a Docker container on your machine.

Installation Methods

Docker Install DXT Extension uvx Development

https://github.com/user-attachments/assets/eb84419a-6eaf-47bd-ac52-37bc59c83680

Usage Examples

What are my recommended jobs I can apply to?

Research the background of this candidate https://www.linkedin.com/in/stickerdaniel/

Get this company profile for partnership discussions https://www.linkedin.com/company/inframs/

Suggest improvements for my CV to target this job posting https://www.linkedin.com/jobs/view/4252026496

Features & Tool Status

[!TIP]

  • Profile Scraping (get_person_profile): Get detailed information from a LinkedIn profile including work history, education, skills, and connections
  • Company Analysis (get_company_profile): Extract comprehensive company information from a LinkedIn company profile name
  • Job Details (get_job_details): Retrieve specific job posting details using LinkedIn job IDs
  • Job Search (search_jobs): Search for jobs with filters like keywords and location
  • Recommended Jobs (get_recommended_jobs): Get personalized job recommendations based on your profile
  • Session Management (close_session): Properly close browser session and clean up resources

[!NOTE] July 2025: All tools are currently functional and actively maintained. If you encounter any issues, please report them in the GitHub issues.



🐳 Docker Setup (Recommended - Universal)

Prerequisites: Make sure you have Docker installed and running.

Installation

Client Configuration:

{
  "mcpServers": {
    "linkedin": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-e", "LINKEDIN_COOKIE",
        "stickerdaniel/linkedin-mcp-server:latest"
      ],
      "env": {
        "LINKEDIN_COOKIE": "li_at=YOUR_COOKIE_VALUE"
      }
    }
  }
}

Getting the LinkedIn Cookie

🌐 Chrome DevTools Guide
  1. Open LinkedIn and login
  2. Open Chrome DevTools (F12 or right-click → Inspect)
  3. Go to Application > Storage > Cookies > https://www.linkedin.com
  4. Find the cookie named li_at
  5. Copy the Value field (this is your LinkedIn session cookie)
  6. Use this value as your LINKEDIN_COOKIE in the configuration
🐳 Docker get-cookie method

Run the server with the --get-cookie flag:

docker run -it --rm \
  stickerdaniel/linkedin-mcp-server:latest \
  --get-cookie

Copy the cookie from the output and set it as LINKEDIN_COOKIE in your client configuration. If this fails with a captcha challenge, use the method above.

[!NOTE] The cookie will expire during the next 30 days. Just get the new cookie and update your client config. There are also many cookie manager extensions that you can use to quickly copy the cookie.

Docker Setup Help

🔧 Configuration

Transport Modes:

  • Default (stdio): Standard communication for local MCP servers
  • Streamable HTTP: For a web-based MCP server

CLI Options:

  • --log-level {DEBUG,INFO,WARNING,ERROR} - Set logging level (default: WARNING)
  • --no-lazy-init - Login to LinkedIn immediately instead of waiting for the first tool call
  • --transport {stdio,streamable-http} - Set transport mode
  • --host HOST - HTTP server host (default: 127.0.0.1)
  • --port PORT - HTTP server port (default: 8000)
  • --path PATH - HTTP server path (default: /mcp)
  • --get-cookie - Attempt to login with email and password and extract the LinkedIn cookie
  • --cookie {cookie} - Pass a specific LinkedIn cookie for login
  • --user-agent {user_agent} - Specify custom user agent string to prevent anti-scraping detection

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

docker run -it --rm \
  -e LINKEDIN_COOKIE="li_at=YOUR_COOKIE_VALUE" \
  -p 8080:8080 \
  stickerdaniel/linkedin-mcp-server:latest \
  --transport streamable-http --host 0.0.0.0 --port 8080 --path /mcp

Test with mcp inspector:

  1. Install and run mcp inspector bunx @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
❗ Troubleshooting

Docker issues:

  • Make sure Docker is installed
  • Check if Docker is running: docker ps

Login issues:

  • Ensure your LinkedIn cookie is set and correct
  • Make sure you have only one active LinkedIn session per cookie at a time. Trying to open multiple sessions with the same cookie will result in a cookie invalid error.
  • LinkedIn may require a login confirmation in the LinkedIn mobile app for --get-cookie
  • You might get a captcha challenge if you logged in a lot of times in a short period of time, then try again later or follow the local setup instructions to run the server manually in --no-headless mode where you can debug the login process (solve captcha manually)


📦 Claude Desktop (DXT Extension)

Prerequisites: Claude Desktop and Docker installed

One-click installation for Claude Desktop users:

  1. Download the DXT extension
  2. Double-click to install into Claude Desktop
  3. Set your LinkedIn cookie in the extension settings

Getting the LinkedIn Cookie

🌐 Chrome DevTools Guide
  1. Open LinkedIn and login
  2. Open Chrome DevTools (F12 or right-click → Inspect)
  3. Go to Application > Storage > Cookies > https://www.linkedin.com
  4. Find the cookie named li_at
  5. Copy the Value field (this is your LinkedIn session cookie)
  6. Use this value as your LINKEDIN_COOKIE in the configuration
🐳 Docker get-cookie method

Run the server with the --get-cookie flag:

docker run -it --rm \
  stickerdaniel/linkedin-mcp-server:latest \
  --get-cookie

Copy the cookie from the output and set it as LINKEDIN_COOKIE in your client configuration. If this fails with a captcha challenge, use the method above.

[!NOTE] The cookie will expire during the next 30 days. Just get the new cookie and update your client config. There are also many cookie manager extensions that you can use to quickly copy the cookie.

DXT Extension Setup Help

❗ Troubleshooting

Docker issues:

  • Make sure Docker is installed
  • Check if Docker is running: docker ps

Login issues:

  • Ensure your LinkedIn cookie is set and correct
  • Make sure you have only one active LinkedIn session per cookie at a time. Trying to open multiple sessions with the same cookie will result in a cookie invalid error.
  • LinkedIn may require a login confirmation in the LinkedIn mobile app for --get-cookie
  • You might get a captcha challenge if you logged in a lot of times in a short period of time, then try again later or follow the local setup instructions to run the server manually in --no-headless mode where you can debug the login process (solve captcha manually)


🚀 uvx Setup (Quick Install - Universal)

Prerequisites: Make sure you have uv installed.

Installation

Run directly from GitHub without cloning:

# Run directly from GitHub (latest version)
uvx --from git+https://github.com/stickerdaniel/linkedin-mcp-server linkedin-mcp-server --help

# Run with your LinkedIn cookie
uvx --from git+https://github.com/stickerdaniel/linkedin-mcp-server linkedin-mcp-server --cookie "li_at=YOUR_COOKIE_VALUE"

Getting the LinkedIn Cookie

🌐 Chrome DevTools Guide
  1. Open LinkedIn and login
  2. Open Chrome DevTools (F12 or right-click → Inspect)
  3. Go to Application > Storage > Cookies > https://www.linkedin.com
  4. Find the cookie named li_at
  5. Copy the Value field (this is your LinkedIn session cookie)
  6. Use this value as your LINKEDIN_COOKIE in the configuration
🚀 uvx get-cookie method

Run the server with the --get-cookie flag:

uvx --from git+https://github.com/stickerdaniel/linkedin-mcp-server \
  linkedin-mcp-server --get-cookie

Copy the cookie from the output and set it as LINKEDIN_COOKIE in your client configuration. If this fails with a captcha challenge, use the method above.

[!NOTE] The cookie will expire during the next 30 days. Just get the new cookie and update your client config. There are also many cookie manager extensions that you can use to quickly copy the cookie.

uvx Setup Help

🔧 Configuration

Client Configuration:

{
  "mcpServers": {
    "linkedin": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/stickerdaniel/linkedin-mcp-server",
        "linkedin-mcp-server"
      ],
      "env": {
        "LINKEDIN_COOKIE": "li_at=YOUR_COOKIE_VALUE"
      }
    }
  }
}

Transport Modes:

  • Default (stdio): Standard communication for local MCP servers
  • Streamable HTTP: For web-based MCP server

CLI Options:

  • --log-level {DEBUG,INFO,WARNING,ERROR} - Set logging level (default: WARNING)
  • --no-lazy-init - Login to LinkedIn immediately instead of waiting for the first tool call
  • --transport {stdio,streamable-http} - Set transport mode
  • --host HOST - HTTP server host (default: 127.0.0.1)
  • --port PORT - HTTP server port (default: 8000)
  • --path PATH - HTTP server path (default: /mcp)
  • --get-cookie - Attempt to login with email and password and extract the LinkedIn cookie
  • --cookie {cookie} - Pass a specific LinkedIn cookie for login
  • --user-agent {user_agent} - Specify custom user agent string to prevent anti-scraping detection

Basic Usage Examples:

# Run with cookie from environment variable
LINKEDIN_COOKIE="YOUR_COOKIE_VALUE" uvx --from git+https://github.com/stickerdaniel/linkedin-mcp-server linkedin-mcp-server

# Run with cookie via flag
uvx --from git+https://github.com/stickerdaniel/linkedin-mcp-server linkedin-mcp-server --cookie "YOUR_COOKIE_VALUE"

# Run with debug logging
uvx --from git+https://github.com/stickerdaniel/linkedin-mcp-server linkedin-mcp-server --log-level DEBUG

# Extract cookie with credentials
uvx --from git+https://github.com/stickerdaniel/linkedin-mcp-server linkedin-mcp-server --get-cookie

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

uvx --from git+https://github.com/stickerdaniel/linkedin-mcp-server linkedin-mcp-server \
  --transport streamable-http --host 127.0.0.1 --port 8080 --path /mcp

Test with mcp inspector:

  1. Install and run mcp inspector bunx @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
❗ Troubleshooting

Installation issues:

  • Ensure you have uv installed: curl -LsSf https://astral.sh/uv/install.sh | sh
  • Check uv version: uv --version (should be 0.4.0 or higher)

Cookie issues:

  • Ensure your LinkedIn cookie is set and correct
  • Cookie can be passed via --cookie flag or LINKEDIN_COOKIE environment variable
  • Make sure you have only one active LinkedIn session per cookie at a time

Login issues:

  • LinkedIn may require a login confirmation in the LinkedIn mobile app for --get-cookie
  • You might get a captcha challenge if you logged in a lot of times in a short period


🐍 Local Setup (Develop & Contribute)

Prerequisites: Chrome browser and Git installed

ChromeDriver Setup:

  1. Check Chrome version: Chrome → menu (⋮) → Help → About Google Chrome
  2. Download matching ChromeDriver: Chrome for Testing
  3. Make it accessible:
    • Place ChromeDriver in PATH (/usr/local/bin on macOS/Linux)
    • Or set: export CHROMEDRIVER_PATH=/path/to/chromedriver
    • if no CHROMEDRIVER_PATH is set, the server will try to find it automatically by checking common locations

Installation

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

# 2. Install UV package manager
curl -LsSf https://astral.sh/uv/install.sh | sh
uv python # install python if you don't have it

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

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

# 5. Start the server once manually
# You will be prompted to enter your LinkedIn credentials, and they will be securely stored in your OS keychain
# Once logged in, your cookie will be stored in your OS keychain and used for subsequent runs until it expires
uv run -m linkedin_mcp_server --no-headless --no-lazy-init

Local Setup Help

🔧 Configuration

CLI Options:

  • --no-headless - Show browser window (debugging)
  • --log-level {DEBUG,INFO,WARNING,ERROR} - Set logging level (default: WARNING)
  • --no-lazy-init - Login to LinkedIn immediately instead of waiting for the first tool call
  • --get-cookie - Login with email and password and extract the LinkedIn cookie
  • --clear-keychain - Clear all stored LinkedIn credentials and cookies from system keychain
  • --cookie {cookie} - Pass a specific LinkedIn cookie for login
  • --user-agent {user_agent} - Specify custom user agent string to prevent anti-scraping detection
  • --transport {stdio,streamable-http} - Set transport mode
  • --host HOST - HTTP server host (default: 127.0.0.1)
  • --port PORT - HTTP server port (default: 8000)
  • --path PATH - HTTP server path (default: /mcp)
  • --help - Show help

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": {
    "linkedin": {
      "command": "uv",
      "args": ["--directory", "/path/to/linkedin-mcp-server", "run", "-m", "linkedin_mcp_server"]
    }
  }
}
❗ Troubleshooting

Login/Scraping issues:

  • Use --no-headless to see browser actions (captcha challenge, LinkedIn mobile app 2fa, ...)
  • Add --no-lazy-init to attempt to login to LinkedIn immediately instead of waiting for the first tool call
  • Add --log-level DEBUG to see more detailed logging
  • Make sure you have only one active LinkedIn session per cookie at a time. Trying to open multiple sessions with the same cookie will result in a cookie invalid error. E.g. if you have a logged in browser session with a docker container, you can't use the same cookie to login with the local setup while the docker container is running / session is not closed.

ChromeDriver issues:

  • Ensure Chrome and ChromeDriver versions match
  • Check ChromeDriver is in PATH or set CHROMEDRIVER_PATH in your env

Python issues:

  • Check Python version: uv python --version (should be 3.12+)
  • Reinstall dependencies: uv sync --reinstall

Feel free to open an issue or PR!



Acknowledgements

Built with LinkedIn Scraper by @joeyism and FastMCP.

⚠️ Use in accordance with LinkedIn's Terms of Service. Web scraping may violate LinkedIn's terms. This tool is for personal use only.

Star History

Star History Chart

License

This project is licensed under the Apache 2.0 license.


Be the First to Experience MCP Now