In-depth architectural comparison of the Linkedin MCP and LinkedIn Sales Navigator 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
Linkedin MCP
Social Media · Local stdio
Quality: 59/100 (Good) | Auth: other
LinkedIn Sales Navigator
Social Media · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Linkedin MCP if you need specialized Social Media tools running via a local process. Choose LinkedIn Sales Navigator 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 Linkedin MCP when:
You need dedicated capabilities in the Social Media domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: LINKEDIN_MCP_SESSION_PATH.
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.
LinkedIn Sales Navigator contact and account search from your logged-in browser.
Report server version, browser/login status, and capabilities.
health_check
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
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).
Linkedin MCP is categorized under Social Media and uses a local stdio subprocess. In contrast, LinkedIn Sales Navigator belongs to Social Media using local stdio subprocess. Select Linkedin MCP when you need capabilities focused on social media and LinkedIn Sales Navigator when you require tools for social media.
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).
+10 more tools listed on main page
LinkedIn Sales Navigator Tools (16)
search_contacts
People/lead search from a Sales Navigator URL. Navigates + paginates in the browser, saves records to SQLite, returns a small progress summary.
search_accounts
Company/account search from a Sales Navigator URL. Same, for accounts.
enrich_leads
Add Open Profile / InMail status to a saved contact search. Costs one LinkedIn request per lead, so it is opt-in and resumable — see [Open Profile status](#open-profile-status).
fetch_lead_profiles
Depth 3: full profiles for drafting (~15 KB/lead). Opt-in via `ENABLE_PROFILE`.
get_lead_profile
Read one stored full profile. Local only, no LinkedIn call.
pipeline_status
One funnel view: scraped → enriched → open → profiled → sent.
reconcile_outreach
Settle sends stuck in `sending` against LinkedIn itself.
run_outreach_batch
Draft and send for several leads in one call via MCP sampling. Same guards; `dry_run` defaults true.
check_replies
Read the inbox and mark leads who answered. Sends nothing.
next_outreach_batch
Leads eligible for a first message — Open Profile first, anyone already contacted excluded. Read-only.
send_message
Send ONE message. The only tool that writes to LinkedIn: off by default, `dry_run=true` by default.
outreach_status
Counts by status and channel, plus remaining daily cap.
+4 more tools listed on main page
H
LinkedIn Sales Navigator vs HeyLead — Autonomous LinkedIn SDR