Linkedin MCP vs PitchGhost — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Linkedin MCP vs PitchGhost
In-depth architectural comparison of the Linkedin MCP and PitchGhost 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: 61/100 (Good) | Auth: other
PitchGhost
Social Media · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Linkedin MCP if you need specialized Social Media tools running via a local process. Choose PitchGhost 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.
AI-powered social listening across Twitter, LinkedIn, Reddit, Facebook, and more.
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").
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, PitchGhost belongs to Social Media using local stdio subprocess. Select Linkedin MCP when you need capabilities focused on social media and PitchGhost when you require tools for social media.