In-depth architectural comparison of the Wenyan 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
Wenyan MCP
Social Media · Remote HTTP/SSE
Quality: 47/100 (Fair) | Auth: other
LinkedIn Sales Navigator
Social Media · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Wenyan MCP if you need specialized Social Media tools running via a hosted cloud SSE transport. 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 Wenyan MCP when:
You need dedicated capabilities in the Social Media domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: WECHAT_APP_ID, WECHAT_APP_SECRET.
Primary tools included: Markdown-to-WeChat rich-text rendering, Built-in and custom formatting themes, Local and remote image uploads.
Wenyan MCP is categorized under Social Media and uses a remote streaming HTTP/SSE transport. In contrast, LinkedIn Sales Navigator belongs to Social Media using local stdio subprocess. Select Wenyan MCP when you need capabilities focused on social media and LinkedIn Sales Navigator when you require tools for social media.
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