Linkedin Company Employees vs Linkedapi MCP
A side-by-side look at the Linkedin Company Employees 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 Company Employees for social media work over a hosted endpoint; 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?
Choose Linkedin Company Employees when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
APIFY_API_TOKEN.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 40/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | APIFY_API_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 70 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Linkedin Company Employees | View Linkedapi MCP |
Tools & capabilities
Linkedin Company Employees tools
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 Company Employees
{
"mcpServers": {
"linkedin-company-employees": {
"url": "https://mcp.apify.com/?tools=actors,docs,johnvc/linkedin-company-employees-api"
}
}
}
Linkedapi MCP
{
"mcpServers": {
"linked-api-linkedapi-mcp": {
"url": "https://linkedapi.io/mcp/installation/"
}
}
}
Frequently asked questions
Linkedin Company Employees is categorized under Social Media and uses a remote HTTP/SSE transport. Linkedapi MCP belongs to Social Media and uses a remote HTTP/SSE transport. Pick Linkedin Company Employees 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 Company Employees has no declared pricing — check the project's own site. 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-company-employees 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 Company Employees has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Linkedapi MCP has 47/100 (Fair) with 4 views, 0 installs and 70 GitHub stars.