A side-by-side look at the LinkFetch: LinkedIn MCP 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 LinkFetch: LinkedIn MCP 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.
LINKFETCH_API_KEY, LINKFETCH_MCP_URL.search_jobs, get_job, search_companies.Rows where the two servers differ are marked.
| Spec | L LinkFetch: LinkedIn MCP | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 53/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | LINKFETCH_API_KEYLINKFETCH_MCP_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 70 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 11 | Not listed |
| Full listing | View LinkFetch: LinkedIn MCP | View Linkedapi MCP |
search_jobsget_jobsearch_companiesget_companyai_scoreai_classifyai_extractai_writelist_leadssave_leadlist_lead_listsNo tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"linkfetch-linkedin-mcp": {
"command": "npx",
"args": [
"-y",
"linkfetch-mcp"
],
"env": {
"LINKFETCH_API_KEY": "YOUR_LINKFETCH_API_KEY_HERE",
"LINKFETCH_MCP_URL": "YOUR_LINKFETCH_MCP_URL_HERE"
}
}
}
}
{
"mcpServers": {
"linked-api-linkedapi-mcp": {
"url": "https://linkedapi.io/mcp/installation/"
}
}
}