A side-by-side look at the LinkedIn 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.
Verdict: choose LinkedIn for social media work as a local process; choose Linkedin MCP Server for social media as a local process. You can also run both side by side in one mcpServers block.
get_profile, get_my_profile, search_people.Rows where the two servers differ are marked.
| Spec | L Linkedin MCP Server | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 51/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 3,961 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 12 | Not listed |
| Full listing | View LinkedIn | View Linkedin MCP Server |
get_profileFetch a member's profile (headline, about, experience, education, skills) by URL or public identifier.get_my_profileFetch the profile of the account this server is logged in as.search_peopleSearch LinkedIn members by keyword.get_inboxList recent message thread previews.get_conversationFetch the full message history of one thread, by id.search_conversationsSearch your message threads by participant or keyword.get_companyFetch a company page (about, size, industry, recent posts).search_companiesSearch LinkedIn companies by keyword.search_jobsSearch job postings by keyword and optional location.get_jobFetch one job posting in full.search_postsSearch LinkedIn feed posts by keyword.linkedin_statusCheck session validity and current usage against the rate limits in [Safety](#safety).No 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": {
"linkedin": {
"command": "uvx",
"args": [
"linkedin-api-mcp"
]
}
}
}
{
"mcpServers": {
"linkedin-mcp-server-3": {
"command": "uvx",
"args": [
"mcp-server-linkedin"
]
}
}
}