openlinkedinmcp

Playwright-powered MCP server for LinkedIn. Automate jobs, profile edits, messaging, network actions, feed posts, and more using a real logged-in browser session.

LinkedIn’s official API cannot cover most member actions. This server drives linkedin.com in Chromium instead. UI changes can break selectors — treat tools as best-effort automation.

Requirements

• Node.js 20+

• Chromium for Playwright (npx playwright install chromium)

Related MCP server: LinkedIn MCP Server

Setup

npm install
npm run build

Install into Cursor / Claude (recommended)

Register this server in your MCP client config (builds if needed, merges without wiping other servers):

./scripts/install.sh            # interactive: Cursor, Claude, or both
./scripts/install.sh --cursor   # ~/.cursor/mcp.json
./scripts/install.sh --claude   # Claude Code (~/.claude.json) and Desktop if present
./scripts/install.sh --both
./scripts/install.sh --dry-run --both   # preview only

Or via npm:

npm run install:mcp -- --cursor

Claude targets: Claude Code CLI (claude mcp add when available, else ~/.claude.json) and Claude Desktop (claude_desktop_config.json on macOS/Linux/Windows when the app config dir exists).

Session data (cookies / browser profile) is stored at:

~/.openlinkedinmcp/browser-profile

Override with OPENLINKEDINMCP_DATA_DIR.

Manual MCP config

If you prefer to edit configs by hand, add (path must be absolute):

{
  "mcpServers": {
    "openlinkedinmcp": {
      "command": "node",
      "args": ["/absolute/path/to/openlinkedinmcp/dist/index.js"],
      "env": {
        "OPENLINKEDINMCP_HEADLESS": "1"
      }
    }
  }
}

Typical locations:

• Cursor: ~/.cursor/mcp.json

• Claude Code: ~/.claude.json

• Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json

• Claude Desktop (Linux): ~/.config/Claude/claude_desktop_config.json

For local iteration without building:

{
  "command": "npx",
  "args": ["tsx", "/absolute/path/to/openlinkedinmcp/src/index.ts"]
}

First-time login

1. Call linkedin_login from your MCP client.

2. A visible browser window opens on LinkedIn’s login page.

3. Sign in (complete 2FA if prompted).

4. When the feed loads, the tool returns success and the session is reused.

Environment flags:

Tools

Auth

• linkedin_login — interactive Playwright login

• linkedin_auth_status

• linkedin_logout

Profile

• get_my_profile, get_profile

• update_headline, update_about

• open_profile_section — experience, education, skills, featured, interests, contact-info

Jobs

• search_jobs, get_job, save_job

• get_saved_jobs, get_job_applications

• easy_apply_job — defaults to dry_run=true

Feed

• get_feed, create_post, like_post, comment_on_post, repost

Messaging

• list_conversations, get_conversation, send_message, start_conversation

Network

• search_people, send_connection_request

• get_pending_invitations, accept_invitation

• get_connections, follow_person

Companies & notifications

• search_companies, get_company, follow_company

• get_notifications

Browser helpers

• navigate, screenshot_page, close_browser

Destructive or outbound actions (create_post, send_message, easy_apply_job, connection requests, etc.) support dry_run where noted. Prefer dry runs until you trust the flow.

Scripts

npm run dev          # stdio MCP via tsx
npm run build        # compile to dist/
npm run typecheck    # tsc --noEmit
npm start            # node dist/index.js
npm run install:mcp  # register with Cursor / Claude (see Setup)

License

MIT (see LICENSE).