Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Enables fetching detailed LinkedIn profile data by automating a browser session with your LinkedIn cookie to access full profiles.

README.md

LinkedIn MCP Server

This is a Model Context Protocol (MCP) server that acts as a bridge to fetch detailed LinkedIn profile data (Experience, Education, About sections) which are typically hidden from the public/lite API.

It uses a Puppeteer wrapper to automate a browser session with your LinkedIn cookie, ensuring it can access the full profile view that you see when logged in.

Features

  • read_linkedin_profile: A tool that takes a LinkedIn profile URL and returns the scraped text content of the profile.

Prerequisities

  • Node.js (v18+)
  • A LinkedIn account
  • Your LinkedIn li_at cookie

Setup

1. Install Dependencies

npm install

2. Configure Environment (Authentication)

This server needs your LinkedIn li_at cookie to view full profiles.

Method A: Automatic (Recommended)

We have included a helper tool to log you in and save the cookie automatically.

  1. Run the auth script:
   npm run auth
  1. A browser window will open. Log in to LinkedIn.
  2. Once you reach the feed, the script will detect the cookie, save it to .env, and close the window automatically.

Method B: Manual

  1. Create a .env file in the root directory.
  2. Open LinkedIn in your browser (Chrome/Edge).
  3. Open Developer Tools (F12 or Right Click -> Inspect).
  4. Go to the Application tab.
  5. Under Storage -> Cookies -> https://www.linkedin.com, find the cookie named li_at.
  6. Copy its value and paste it into .env:
   LINKEDIN_LI_AT_COOKIE="your_cookie_value_here"

3. Build the Server

npm run build
# OR
npx tsc

(Note: npm run build is not currently defined in package.json, so use npx tsc or add the script.)

Usage with Antigravity / Claude Desktop

Add the server to your MCP configuration file (e.g., claude_desktop_config.json):

{
  "mcpServers": {
    "linkedin-reference": {
      "command": "node",
      "args": ["/absolute/path/to/linkedin-mcp-server/dist/index.js"],
      "env": {
        "LINKEDIN_LI_AT_COOKIE": "your_cookie_value_if_not_using_dotenv"
      }
    }
  }
}

How It Works

  1. The MCP client sends a read_linkedin_profile request with a URL.
  2. The server launches a headless Puppeteer browser.
  3. It injects the li_at cookie to authenticate as you.
  4. It navigates to the profile URL.
  5. It extracts the innerText of the page body (simple approach).
  6. It returns the text to the LLM for processing.

Project Structure

  • src/index.ts: Main server entry point and tool logic.
  • scripts/validate_mcp.mjs: A validation script to test if the server boots up correctly.
  • dist/: Compiled JavaScript files.

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Browser & Scraping servers.