MCP Linkedin vs Linkedin MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Linkedin vs Linkedin MCP
In-depth architectural comparison of the MCP Linkedin and Linkedin MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Linkedin
Social Media · Local stdio
Quality: 41/100 (Fair) | Auth: API Key required
Linkedin MCP
Social Media · Local stdio
Quality: 61/100 (Good) | Auth: other
Verdict Summary: Choose MCP Linkedin if you need specialized Social Media tools running via a local process. Choose Linkedin MCP if your workspace requires Social Media integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Linkedin when:
You need dedicated capabilities in the Social Media domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: UNIPILE_API_KEY, UNIPILE_DSN.
Primary tools included: LinkedIn post publishing through Unipile, Dry-run previews for posts and comments, Comments and immediate reactions.
LinkedIn publishing, commenting, and reacting via Unipile API. Dry-run by default, SKILL.md included, CLI-first design for AI automation workflows.
LinkedIn for AI assistants over an authenticated browser session — profiles, people/job/company search, feed, messaging, and gated writes (connect, message, post, react, comment) returned as structured JSON, with built-in rate limiting. npx -y linkedin-mcp-tools.
Category & Scope
Tools & Capabilities Breakdown
MCP Linkedin Tools (5)
LinkedIn post publishing through Unipile
Dry-run previews for posts and comments
Comments and immediate reactions
Local or URL-based media attachments
Company mention resolution
Linkedin MCP Tools (22)
whoami
Report server version, browser/login status, and capabilities.
health_check
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP Linkedin is categorized under Social Media and uses a local stdio subprocess. In contrast, Linkedin MCP belongs to Social Media using local stdio subprocess. Select MCP Linkedin when you need capabilities focused on social media and Linkedin MCP when you require tools for social media.
Deep health check: cookie login state, a LIVE Voyager probe (confirms the API actually answers, not just that a cookie exists), and today's safety-budget headroom (per-action used/cap/remaining + pending invites).
close_session
Close the browser context and release resources (kills the Chrome process).
get_my_profile
Get the authenticated user's own LinkedIn profile (experience, education, headline, summary).
get_profile
Get a LinkedIn profile by public identifier (the slug in the profile URL, e.g. "satyanadella").
get_feed
Get recent posts from your LinkedIn home feed (author + post text).
get_notifications
Get your recent LinkedIn notifications (headline, time, read state).
search_people
Search LinkedIn people by keywords. Returns name, headline, location, and public identifier (pass that to get_profile for full details).
search_jobs
Search LinkedIn jobs by keywords (and optional location). Returns title, location, posted time.
get_inbox
List your recent LinkedIn messaging conversations (title, last activity, unread count).
get_job_details
Get full details for a job posting by its numeric id (the digits in /jobs/view/<id> or from search_jobs jobUrn).
search_companies
Search LinkedIn companies by keywords. Returns name + universalName slug (pass that to get_company for full details).