C — Moderate risk signals Graded October 16, 2026Several concerns worth a closer look before you install.Based on public adoption and transparency signals as of October 16, 2026. Our opinion, not a code audit or security guarantee.
App connector · Files & documents, Communication
linkedin-mcp-server
Open-source MCP server for LinkedIn. Give Claude and any MCP-compatible AI agent access to profiles, companies, jobs, and messages.
Bottom line: Signal-based grade (3/7 points): well starred on GitHub, public source code. This reflects adoption and transparency, not a code review.
- Popularity score
- 41/100
- Rank
- #314 of 500
- GitHub stars
- 3.9k
What it does
linkedin-mcp-server is an open-source MCP (Model Context Protocol) connector that grants Claude and other AI agents programmatic access to LinkedIn data including profiles, companies, job listings, and messages. It bridges LinkedIn's API with MCP-compatible AI systems, enabling agents to read and potentially interact with LinkedIn content.
Who it’s for
Builders integrating AI agents with LinkedIn workflows, and executives exploring AI automation for recruitment, sales outreach, or professional intelligence gathering. Best suited for teams with technical infrastructure to host and manage the connector.
Copy-paste setup
Check these steps against the project’s own instructions before running anything.
Verify against the repo README at https://github.com/stickerdaniel/linkedin-mcp-server (opens external site) for current instructions. Typically involves cloning the repo, installing Node.js dependencies, configuring LinkedIn API credentials, and adding the server to Claude Desktop's mcpServers config or your MCP-compatible AI platform's connector settings. Exact steps should be confirmed in the official repository.
Risks
- Credential exposure: Requires LinkedIn API credentials (session tokens or OAuth); misconfiguration or logs could leak authentication secrets that grant broad account access
- Data exfiltration: Agent could be prompted to extract and forward sensitive LinkedIn data (profiles, messages, contact lists) to external systems or malicious actors
- Prompt injection: Untrusted prompts could manipulate the agent into performing unintended LinkedIn actions (messaging, endorsements, applying to jobs)
- Third-party maintenance: Dependency on open-source maintainer for security patches; 0 weekly npm downloads suggest limited adoption and slower vulnerability response
- LinkedIn ToS violation: Automated access to LinkedIn data may violate platform terms of service, risking account suspension or legal action
How to stay secure
Least-privilege permissions
- Create a dedicated LinkedIn account for the AI agent instead of using your personal or business account—this limits damage if credentials are stolen
- Restrict API access scope to only the data the agent actually needs (for example, "read profiles only" rather than "read and send messages")
- Use temporary credentials with expiration dates instead of permanent tokens; rotate them monthly or after each major task
- Never share credentials in emails, chat logs, or configuration files; store them in a password manager or secure vault only the AI system can access
Network isolation
- Run the connector on a separate internal machine (not your main computer) that has limited internet access and doesn't contain other sensitive business data
- Block outbound connections from the machine running the connector to any external websites or cloud services except LinkedIn's official servers
- Use a firewall rule to restrict which internal systems the connector machine can communicate with, and only allow the minimum needed
- Avoid connecting it to public networks or WiFi; use a dedicated wired connection or isolated network segment
Monitoring
- Log all actions the agent performs (which profiles it viewed, what messages it sent, what data it extracted) and review logs weekly for suspicious activity
- Set up alerts if the connector tries to access LinkedIn data outside normal business hours or attempts unusual actions like bulk messaging
- Monitor your LinkedIn account for unexpected login locations, failed access attempts, or changes to account settings
- Track API usage and flag any spikes in data downloads or requests that don't match your expected workload
Red flags to watch for
- The connector requesting additional permissions it didn't need before, or asking you to disable security features
- Unusual LinkedIn notifications about logins, password changes, or access from unfamiliar devices or locations
- The maintainer becomes unresponsive to security vulnerability reports or stops releasing updates for months
- Your AI agent suddenly starts suggesting actions you didn't request, like messaging contacts or applying to jobs—this signals potential prompt injection or compromise
Alternatives
- Proxycurl API – Commercial REST API for LinkedIn scraping with built-in rate limiting and ToS compliance; integrates via custom MCP connectors
- n8n LinkedIn integration – Low-code workflow automation with LinkedIn without building custom agents; pre-built nodes and credential management
- Zapier + LinkedIn – No-code automation for LinkedIn notifications, lead capture, and CRM syncs; limited to predefined workflows
- Official LinkedIn API (Talent Solutions) – Native Microsoft partnership for recruitment and premium data; higher cost and stricter approval process