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
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
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 48,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 AI agents to interact with LinkedIn through MCP tools for retrieving company profiles, posts, insights, and person profiles, as well as a prompt for account research.

README.md

LinkedIn MCP Server (AI version)

A powerful Model Context Protocol server that exposes verified LinkedIn capabilities as MCP tools, plus an account-research prompt — runnable over stdio (local) and Streamable HTTP (remote).

Built as the reference implementation for the course in ../Documentation/. Scope: LinkedIn-only (Tier A verified core + Tier D extended). See PLAN.md.

Tools

| Tool | What it does | |---|---| | linkedin_get_company_profile | Company name, industry, size, HQ, specialities | | linkedin_get_company_posts | Recent company posts with engagement | | linkedin_get_company_insights | Headcount growth, hiring signals, people highlights | | linkedin_search_company_leaders | Leadership-level people at a company | | linkedin_get_person_profile | A person's profile | | linkedin_get_person_posts | A person's recent posts | | _Tier D (extended)_ | company/people/job search, contact info — added in Phase 4 |

Prompt: account_intel — scripts the tools into a full company brief.

Setup

uv sync --extra dev
cp .env.example .env        # then fill in LI_AT + LI_JSESSIONID

Run

# stdio (default) — for local hosts / the Inspector
uv run linkedin-mcp

# Streamable HTTP — secured (Origin allowlist + bearer token), localhost-bound
uv run linkedin-mcp --transport http

Verify in the MCP Inspector

npx @modelcontextprotocol/inspector uv run linkedin-mcp

List tools, then call linkedin_get_company_profile with {"linkedin_url_or_slug": "microsoft"}.

Plug into Claude Desktop (stdio)

{
  "mcpServers": {
    "linkedin": {
      "command": "uv",
      "args": ["run", "--directory", "C:/Users/WELCOME/Desktop/Linked-MCP/ai-version", "linkedin-mcp"]
    }
  }
}

Notes & safety

  • Unofficial linkedin-api: cookie auth (LI_AT + LI_JSESSIONID) is the

supported path; password login often hits a challenge. Cookies expire → tools return a clear auth error.

  • Rate limits are real; post counts are clamped. Heavy use can flag the account.
  • stdio writes JSON-RPC on stdout — all logs go to stderr only.
  • HTTP proxies your LinkedIn identity: set MCP_AUTH_TOKEN and keep the bind on

localhost before sharing.

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Search servers.