In-depth architectural comparison of the Linkedin Mcp Server and Bluesky Social 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
Linkedin Mcp Server
Social Media · Local stdio
Quality: 44/100 (Fair) | Auth: OAuth 2.0
Bluesky Social Mcp
Social Media · Local stdio
Quality: 35/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Linkedin Mcp Server if you need specialized Social Media tools running via a local process. Choose Bluesky Social 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 Linkedin Mcp Server when:
You need dedicated capabilities in the Social Media domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: LINKEDIN_ACCESS_TOKEN.
Primary tools included: Create, edit, delete LinkedIn posts, Upload images for posts, Fetch user profile details.
Local LinkedIn MCP server for posting to LinkedIn from Claude. 9 tools — create/edit/delete posts (text, image, article), upload images, fetch profile, look up company pages, and check follower counts. Uses the official LinkedIn REST API with OAuth 2.0 (wmembersocial, OIDC).
An MCP server for interacting with Bluesky via the atproto client.
Linkedin Mcp Server is categorized under Social Media and uses a local stdio subprocess. In contrast, Bluesky Social Mcp belongs to Social Media using local stdio subprocess. Select Linkedin Mcp Server when you need capabilities focused on social media and Bluesky Social Mcp when you require tools for social media.