Skip to main content
mcpSource-backed

LinkedIn MCP Server

MCP server that lets Claude use an authenticated LinkedIn browser session to inspect profiles, companies, jobs, feeds, inboxes, and conversations.

by Daniel Sticker · submitted by oktofeesh1·added 2026-06-05·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/stickerdaniel/linkedin-mcp-server/blob/main/README.md, https://github.com/stickerdaniel/linkedin-mcp-server
Brand
LinkedIn MCP Server
Brand domain
github.com
Safety notes
LinkedIn MCP Server uses browser automation against an authenticated LinkedIn account., Tools can read profile, company, job, feed, inbox, and conversation data available to the authenticated session., Some tools can initiate social or messaging actions, such as sending messages or connection requests, so require explicit human confirmation before any account-write action., The server stores browser profile state locally and provides logout/profile management options that can clear authentication state., Respect LinkedIn account rules, rate limits, consent boundaries, and workplace policies before scraping, messaging, or automating professional-network workflows.
Privacy notes
LinkedIn profile data, search queries, company data, job details, inbox metadata, conversation text, feed posts, messages, connection notes, browser cookies, prompts, and tool outputs may be visible to the MCP client and model provider., LinkedIn data can include personal information, employment history, contact details, recruiting plans, sales targets, private messages, and relationship context., Treat the persisted browser profile as sensitive account state and avoid exposing it through logs, screenshots, shared volumes, or untrusted containers.
Author
Daniel Sticker
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

15 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first.

0/5 ready
Account & credentials2Install & runtime1General215 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 3 privacy notes across 6 risk areas. Review closely: credentials & tokens, network access, third-party handling.

6 areas
  • SafetyGeneralLinkedIn MCP Server uses browser automation against an authenticated LinkedIn account.
  • SafetyCredentials & tokensTools can read profile, company, job, feed, inbox, and conversation data available to the authenticated session.
  • SafetyNetwork accessSome tools can initiate social or messaging actions, such as sending messages or connection requests, so require explicit human confirmation before any account-write action.
  • SafetyLocal filesThe server stores browser profile state locally and provides logout/profile management options that can clear authentication state.
  • SafetyNetwork accessRespect LinkedIn account rules, rate limits, consent boundaries, and workplace policies before scraping, messaging, or automating professional-network workflows.
  • PrivacyThird-party handlingLinkedIn profile data, search queries, company data, job details, inbox metadata, conversation text, feed posts, messages, connection notes, browser cookies, prompts, and tool outputs may be visible to the MCP client and model provider.
  • PrivacyData retentionLinkedIn data can include personal information, employment history, contact details, recruiting plans, sales targets, private messages, and relationship context.
  • PrivacyLocal filesTreat the persisted browser profile as sensitive account state and avoid exposing it through logs, screenshots, shared volumes, or untrusted containers.

Safety notes

  • LinkedIn MCP Server uses browser automation against an authenticated LinkedIn account.
  • Tools can read profile, company, job, feed, inbox, and conversation data available to the authenticated session.
  • Some tools can initiate social or messaging actions, such as sending messages or connection requests, so require explicit human confirmation before any account-write action.
  • The server stores browser profile state locally and provides logout/profile management options that can clear authentication state.
  • Respect LinkedIn account rules, rate limits, consent boundaries, and workplace policies before scraping, messaging, or automating professional-network workflows.

Privacy notes

  • LinkedIn profile data, search queries, company data, job details, inbox metadata, conversation text, feed posts, messages, connection notes, browser cookies, prompts, and tool outputs may be visible to the MCP client and model provider.
  • LinkedIn data can include personal information, employment history, contact details, recruiting plans, sales targets, private messages, and relationship context.
  • Treat the persisted browser profile as sensitive account state and avoid exposing it through logs, screenshots, shared volumes, or untrusted containers.

Prerequisites

  • Python 3.12 through 3.14 available to the MCP client runtime.
  • uvx available for package execution.
  • LinkedIn account access for the workflows you want Claude to perform.
  • One-time browser login, including any LinkedIn two-factor, mobile confirmation, or captcha challenge.
  • Local storage available for the persisted LinkedIn browser profile and Patchright browser cache.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
15 minutes
Difficulty
advanced
Full copyable content
{
  "mcpServers": {
    "linkedin": {
      "command": "uvx",
      "args": ["linkedin-scraper-mcp@latest"],
      "env": {
        "UV_HTTP_TIMEOUT": "300"
      }
    }
  }
}

About this resource

Content

LinkedIn MCP Server connects MCP clients to LinkedIn through an authenticated browser session. It can inspect people profiles, the authenticated user's own profile, sidebar profile recommendations, inboxes, conversations, companies, company posts, employees, people search, job search, job details, and feed content. It also exposes action-oriented tools for messages and connection requests that should stay behind explicit approval.

The upstream README documents uvx, Docker, MCPB, and Streamable HTTP setup paths. The supported PyPI package is linkedin-scraper-mcp, which exposes both linkedin-scraper-mcp and linkedin-mcp-server console scripts.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live repository and PyPI metadata for current package version, command name, Python requirement, dependencies, authentication behavior, supported tools, and setup guidance.

Features

  • Read LinkedIn person profiles with selectable sections.
  • Read the authenticated user's own profile.
  • Search people by keyword, location, connection degree, and company.
  • Inspect company profiles, company posts, employees, and company search.
  • Search jobs and retrieve job details.
  • Read recent feed posts from the authenticated account.
  • Read inbox and conversation data available to the session.
  • Send messages or connection requests when explicitly approved.
  • Reuse a persisted browser profile after interactive login.

Installation

For MCP clients that launch stdio servers:

{
  "mcpServers": {
    "linkedin": {
      "command": "uvx",
      "args": ["linkedin-scraper-mcp@latest"],
      "env": {
        "UV_HTTP_TIMEOUT": "300"
      }
    }
  }
}

Restart the MCP client after adding the server. On first use, complete the interactive LinkedIn login flow in the browser window before retrying LinkedIn tools.

Use Cases

  • Ask Claude to inspect a LinkedIn profile before a recruiting or sales call.
  • Search for people by company, location, keyword, or connection degree.
  • Research company profiles, posts, employees, and open roles.
  • Summarize job details for a candidate or hiring workflow.
  • Review inbox or conversation context before drafting a reply.
  • Draft a connection note or message for human approval before sending.

Safety and Privacy

LinkedIn automation operates through a real authenticated account. Keep message sending, connection requests, and other account-write actions behind explicit human confirmation. Avoid broad scraping, high-volume automation, or workflows that violate LinkedIn rules, workplace policy, or recipient consent.

The persisted browser profile, cookies, LinkedIn messages, profile data, company research, job searches, feed content, and relationship context are sensitive. Treat local profile directories and mounted volumes as account secrets, and avoid sharing logs or screenshots that expose LinkedIn session state.

Duplicate Check

No stickerdaniel/linkedin-mcp-server entry, linkedin-scraper-mcp package entry, or matching source URL was found in content/mcp.

Source citations

Add this badge to your README

Show that LinkedIn MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/linkedin-mcp-server.svg)](https://heyclau.de/entry/mcp/linkedin-mcp-server)

How it compares

LinkedIn MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

2 trust signals differ across this comparison (Source provenance, Submitter).

Field

MCP server that lets Claude use an authenticated LinkedIn browser session to inspect profiles, companies, jobs, feeds, inboxes, and conversations.

Open dossier

DataForB2B remote MCP server exposing people and company search, enrichment, and agentic discovery over 800M+ profiles and 75M+ companies via streamable HTTP.

Open dossier

AgentDM provides a hosted MCP grid for agent-to-agent messaging with OAuth or API key auth at the documented grid endpoint.

Open dossier

AgentTrust stdio MCP server giving AI agents verified identity with email, instant messaging, and cloud file storage across 19 Ed25519-signed tools.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceDiffersSource-backedSubmission linkedSource submissionSubmission linkedSource submissionSubmission linkedSource submission
SubmitterDiffersoktofeesh1kiannidevkiannidevkiannidev
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorDaniel StickerDataForB2BAgentDMAgentTrust
Added2026-06-052026-06-142026-06-172026-06-14
Platforms
Harness
Source repo
Safety notesLinkedIn MCP Server uses browser automation against an authenticated LinkedIn account. Tools can read profile, company, job, feed, inbox, and conversation data available to the authenticated session. Some tools can initiate social or messaging actions, such as sending messages or connection requests, so require explicit human confirmation before any account-write action. The server stores browser profile state locally and provides logout/profile management options that can clear authentication state. Respect LinkedIn account rules, rate limits, consent boundaries, and workplace policies before scraping, messaging, or automating professional-network workflows.People search and enrichment tools can return emails, titles, and employer metadata; handle as regulated personal data. Agentic search may issue broader queries than manual filters; review results before automated outreach. Bearer tokens grant billable API access; store them in MCP headers or env vars, not in chat. Do not use exported contact data for unsolicited outreach that violates local privacy laws.send_message and related tools can deliver content to other agents or channels. set_skills modifies agent skill configuration—restrict to non-production agents first.Email tools can send outbound mail from your `@agenttrust.ai` address. Messaging tools can contact other agents and escalate to humans via HITL flows. Drive tools upload, download, and delete files—confirm destructive operations. Ed25519 signing keys are generated locally; back up `~/.agenttrust` before rotation.
Privacy notesLinkedIn profile data, search queries, company data, job details, inbox metadata, conversation text, feed posts, messages, connection notes, browser cookies, prompts, and tool outputs may be visible to the MCP client and model provider. LinkedIn data can include personal information, employment history, contact details, recruiting plans, sales targets, private messages, and relationship context. Treat the persisted browser profile as sensitive account state and avoid exposing it through logs, screenshots, shared volumes, or untrusted containers.Search filters, domains, and profile identifiers are processed by DataForB2B and its data vendors. API keys are credentials; rotate them if exposed in logs, issues, or shared connector configs. Data is sourced from publicly available and verified sources per DataForB2B compliance statements.Messages, channel metadata, and agent lists enter MCP client context and vendor logs. Store Bearer tokens in secret managers—not repository files.Email bodies, attachments, messages, and uploaded files are processed by AgentTrust. Signing keys and API keys are stored locally with 0600 permissions but still require host protection. Outbound email from address is enforced server-side to your agent's `@agenttrust.ai` identity.
Prerequisites
  • Python 3.12 through 3.14 available to the MCP client runtime.
  • uvx available for package execution.
  • LinkedIn account access for the workflows you want Claude to perform.
  • One-time browser login, including any LinkedIn two-factor, mobile confirmation, or captcha challenge.
  • DataForB2B API key with an active credit plan from https://dataforb2b.ai.
  • Claude Pro, Team, or Enterprise with Connectors support, or another MCP client with remote HTTP transport.
  • Compliance review for GDPR and CCPA obligations when exporting people or company data.
  • Understanding that each successful search or enrichment consumes credits.
  • AgentDM account at agentdm.ai.
  • OAuth client setup or API key for Bearer authentication.
  • Review of which agents and channels the MCP client may message.
  • AgentTrust account with a registered agent and API key (`atk_...`).
  • Node.js for the `@agenttrust/mcp-server` npm package.
  • Claude Desktop, Claude Code, Cursor, or another MCP client with stdio transport.
  • Optional interactive setup via `npx @agenttrust/mcp-server init` for Ed25519 signing keys.
Install
uvx linkedin-scraper-mcp@latest
claude mcp add --transport http dataforb2b https://mcp.dataforb2b.ai/mcp
claude mcp add --transport http agentdm https://api.agentdm.ai/mcp/v1/grid --header "Authorization: Bearer YOUR_TOKEN"
claude mcp add agenttrust -- npx -y @agenttrust/mcp-server
Config
{
  "mcpServers": {
    "linkedin": {
      "command": "uvx",
      "args": ["linkedin-scraper-mcp@latest"],
      "env": {
        "UV_HTTP_TIMEOUT": "300"
      }
    }
  }
}
{
  "mcpServers": {
    "dataforb2b": {
      "url": "https://mcp.dataforb2b.ai/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer YOUR_DATAFORB2B_API_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "agentdm": {
      "url": "https://api.agentdm.ai/mcp/v1/grid",
      "type": "http",
      "headers": {
        "Authorization": "Bearer agentdm_..."
      }
    }
  }
}
{
  "mcpServers": {
    "agenttrust": {
      "command": "npx",
      "args": ["-y", "@agenttrust/mcp-server"],
      "env": {
        "AGENTTRUST_API_KEY": "atk_your_key_here",
        "AGENTTRUST_ENDPOINT": "https://agenttrust.ai"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.