Labsco
MCP SERVER

LinkedIn MCP

by stickerdaniel

Read LinkedIn from an agent — profiles, companies, jobs, posts and your own inbox — through your signed-in session.

Social Media Accounts & PostingOfficial source
Summary
One session covers the reading you would otherwise do in twenty tabs.

What it takes off you is the paging: a company's people, its recent posts and the jobs under it come back as data in one pass. Because it acts as you, remember that a message or a connection request is visible to a real person on the other end.

What it is

A browser-driven LinkedIn server, nineteen tools, working as you: your own profile and feed, your inbox, your saved jobs, and the search pages you would otherwise open one at a time. It drives a Patchright Chromium browser and keeps the session between calls.

What you get
  • Profiles by username, your own included, plus the recommendation panels a profile page carries (`get_person_profile`, `get_my_profile`, `get_sidebar_profiles`)
  • People and company search, and your own feed (`search_people`, `search_companies`, `get_feed`)
  • Company pages, their recent posts, and their employee list (`get_company_profile`, `get_company_posts`, `get_company_employees`)
  • Job search with LinkedIn's own filters, job details by id, and the jobs you saved (`search_jobs`, `get_job_details`, `get_saved_jobs`)
  • Global post search, which catches the informal hiring posts that appear before a formal listing does (`search_posts`)
  • Your inbox: conversations listed, read and searched by keyword, and messages sent (`get_inbox`, `get_conversation`, `search_conversations`, `send_message`)
  • A connection request sent to someone you found (`connect_with_person`), and the browser session closed when the work is done (`close_session`)
Requirements

Uv, and a signed-in LinkedIn session — every call goes through a browser as you. `uvx mcp-server-linkedin@latest` prepares its Chromium cache under `~/.linkedin-mcp/patchright-browsers` in the background and opens a login window on the first call that needs it; `--login` does it up front instead. Early calls may return a setup-in-progress error until that finishes. There are also a Claude Desktop bundle and a Docker image, where the session lives in a mounted `~/.linkedin-mcp` volume and login runs through a browser viewer that times out after 30 minutes. Staying on `@latest` is what keeps it working as LinkedIn's page structure changes, and an optional `PROXY_SERVER` routes only the browser traffic.

Setup effort

One command — uvx mcp-server-linkedin@latest