LinkedIn MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add linkedin-api-mcp -- uvx linkedin-api-mcp

{
  "mcpServers": {
    "linkedin-api-mcp": {
      "args": [
        "linkedin-api-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.linkedin-api-mcp]
command = "uvx"
args = ["linkedin-api-mcp"]

{
  "mcpServers": {
    "linkedin-api-mcp": {
      "args": [
        "linkedin-api-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "linkedin-api-mcp": {
      "args": [
        "linkedin-api-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: LINKEDIN_COOKIE (Your LinkedIn li_at session cookie. Optional if you have already stored it in the OS keyring with `linkedin-api-mcp auth`, which is the recommended route: this cookie is equivalent to being logged in as you.), LINKEDIN_HEADLESS (Run the browser headless. Defaults to true; set to 0 to watch what it does.), LINKEDIN_MIN_INTERVAL (Minimum seconds between LinkedIn actions. Defaults to 2.), LINKEDIN_MAX_PER_HOUR (Hard ceiling on LinkedIn actions per rolling hour. Defaults to 120. The server refuses past this rather than sleeping, so an agent in a loop is told to stop.). The author declared them in the registry entry; get the values from the project itself.