A side-by-side look at the Linkedin MCP Server and Linkedapi MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Linkedin MCP Server for social media work as a local process; choose Linkedapi MCP for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
L
Choose Linkedin MCP Server when
You need dedicated capabilities in the Social Media domain.
No tool names declared yet. Check the project README from the listing page.
Linkedapi MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Linkedin MCP Server is categorized under Social Media and uses a local stdio subprocess. Linkedapi MCP belongs to Social Media and uses a remote HTTP/SSE transport. Pick Linkedin MCP Server for social media work and Linkedapi MCP for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Linkedin MCP Server is listed as free. Auth: other. Linkedapi MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add linkedin-mcp-server-3 and linked-api-linkedapi-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Linkedin MCP Server has a quality signal of 57/100 (Good) with 1 views, 0 installs and 3,961 GitHub stars. Linkedapi MCP has 47/100 (Fair) with 4 views, 0 installs and 70 GitHub stars.