LinkedIn MCP Server

OpenSSF Scorecard

Disclaimer: LinkedIn is a registered trademark of LinkedIn Corporation and its affiliates. LinkedIn MCP Server is an independent, unofficial project and is not affiliated with, endorsed by, sponsored by, or associated with LinkedIn Corporation or its affiliates.

A LinkedIn MCP server to find jobs, search people, research companies, manage your network, publish and engage with posts, and read or send messages.

⚡ Quickstart

1. Connect Claude Code

claude mcp add --scope user --transport stdio linkedin-mcp -- \
  uvx --from linkedin-mcp-local linkedin-mcp serve --transport stdio

2. Sign in to LinkedIn

Restart Claude Code. A dedicated browser window opens automatically—sign in to LinkedIn and complete any required verification.

Supported platforms

The server runs natively on Windows, macOS, and Linux. CI executes the complete offline suite on Windows, macOS, Linux x86-64, and Linux ARM64. Browser and OS version requirements follow the official Playwright Python system requirements.

3. Try your first request

Find remote software engineering jobs in India posted on LinkedIn this week.

🛠️ Tools

NOT CHECKED tools remain covered by the offline simulator on every pull request.

See the capability matrix for exact filters, supported formats, inputs, outputs, limits, and unsupported features.

📦 Installation

claude mcp add --scope user --transport stdio linkedin-mcp -- \
  uvx --from linkedin-mcp-local linkedin-mcp serve --transport stdio

codex mcp add linkedin-mcp -- \
  uvx --from linkedin-mcp-local linkedin-mcp serve --transport stdio

{
  "servers": {
    "linkedin-mcp": {
      "command": "uvx",
      "args": ["--from", "linkedin-mcp-local", "linkedin-mcp", "serve", "--transport", "stdio"]
    }
  }
}

{
  "context_servers": {
    "linkedin-mcp": {
      "command": "uvx",
      "args": ["--from", "linkedin-mcp-local", "linkedin-mcp", "serve", "--transport", "stdio"]
    }
  }
}

goose session --with-extension \
  "uvx --from linkedin-mcp-local linkedin-mcp serve --transport stdio"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "linkedin-mcp": {
        "type": "local",
        "command": ["uvx", "--from", "linkedin-mcp-local", "linkedin-mcp", "serve", "--transport", "stdio"]
      }
    }
  }
}

💡 Examples

Find jobs

Find remote software engineering jobs in India posted on LinkedIn this week with Easy Apply.

Research people

Find LinkedIn profiles for engineering managers at Stripe in India and show me their relevant experience.

Research companies

Find fintech companies in Bengaluru on LinkedIn with 51–200 employees and summarize each company.

Explore posts

Find recent LinkedIn posts about AI agents and summarize the most useful discussions.

Manage your network

Show my latest received connection requests on LinkedIn.

Send a LinkedIn connection request to <profile URL> with the note <note>.

Send messages

Send <message> on LinkedIn to <profile URL>.

🏗️ Architecture

[Claude | Codex | Cursor | ...]
               |
       stdio / loopback HTTP
               v
      [Typed MCP boundary]
               |
               v
       [Fair queue + pacing]
               |
      one operation at a time
               v
[Capability executor] ---> [Process-local calls, cursors, evidence]
               |
               v
      [Capability page objects]
               |
               v
[Browser manager: fresh page per call] <--> [Persistent auth profile]
               |
        visible web UI only
               v
           [LinkedIn]

Everything runs locally. There is no hosted backend, telemetry, database, external queue, LangGraph runtime, or credential service. Browser cookies live only in the local Playwright profile. The first client starts one shared local runtime; later clients attach to it, and fair scheduling gives each client a turn between complete tool calls. Operation state lasts only for that runtime. Read the full architecture and privacy policy.

🔒 Privacy Policy

The server has no maintainer-operated backend, analytics, advertising, or telemetry. LinkedIn receives normal visible-UI requests, and the invoking MCP client receives tool results under its own data policy; the project sends nothing to the maintainer. Read the complete privacy policy for processing, storage, sharing, retention, and deletion details.

🛡️ Safety

Use of this software is at your own risk. You are solely responsible for complying with LinkedIn's User Agreement, applicable laws, and third-party rights. LinkedIn may limit or restrict accounts that use prohibited automation. The maintainers do not authorize spam, unauthorized data collection, privacy violations, or circumvention of access controls.

• Use only accounts and activity you are authorized to operate.
• The server pauses on authentication expiry, checkpoints, restriction pages, permission failures, and configuration errors.
• It does not implement CAPTCHA bypass, proxy rotation, fingerprint spoofing, credential harvesting, stealth plugins, or private LinkedIn endpoints.
• Never commit or share the persistent browser profile or local assets.

See SECURITY.md and the security design.

📚 More documentation

• Configuration
• Capability matrix
• Architecture
• Testing
• Collection verification
• Distribution and registry coverage
• Publishing
• Changelog

❤️ Support the project

If LinkedIn MCP Server is useful to you:

• Star the repository
• Sponsor continued development

🌐 Let's connect

Have feedback or an idea for LinkedIn MCP Server?

• Connect with me on LinkedIn
• Follow me on GitHub
• Report a bug or request a feature

⚖️ License

Licensed under the Apache License 2.0.