Linkedapi MCP vs Linkedin MCP Server
A side-by-side look at the Linkedapi MCP and Linkedin MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
Linkedin MCP ServerSocial MediaModel Context Protocol (MCP) server for LinkedIn API integration39FairAuth: oauth 2.0Verdict: choose Linkedapi MCP for social media work over a hosted endpoint; choose Linkedin MCP Server for social media. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Linkedapi MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
LChoose Linkedin MCP Server when
- You need dedicated capabilities in the Social Media domain.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
LINKEDIN_CLIENT_ID, LINKEDIN_CLIENT_SECRET.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Linkedin MCP Server | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 47/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | API key required | OAuth 2.0 |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | LINKEDIN_CLIENT_IDLINKEDIN_CLIENT_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 70 | 54 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Linkedapi MCP | View Linkedin MCP Server |
Tools & capabilities
Linkedapi MCP tools
No tool names declared yet. Check the project README from the listing page.
Linkedin MCP Server 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.
Linkedapi MCP
{
"mcpServers": {
"linked-api-linkedapi-mcp": {
"url": "https://linkedapi.io/mcp/installation/"
}
}
}
Linkedin MCP Server
No confirmed install command for Linkedin MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Linkedapi MCP is categorized under Social Media and uses a remote HTTP/SSE transport. Linkedin MCP Server belongs to Social Media and uses an install path we have not confirmed yet. Pick Linkedapi MCP for social media work and Linkedin MCP Server 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 has no confirmed install command yet — follow its own setup instructions.
Linkedapi MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Linkedin MCP Server has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 linked-api-linkedapi-mcp and linkedin-mcp-server-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Linkedapi MCP has a quality signal of 47/100 (Fair) with 4 views, 0 installs and 70 GitHub stars. Linkedin MCP Server has 39/100 (Fair) with 0 views, 0 installs and 54 GitHub stars.