linkedin-mcp-server
Related Servers
Alternatives to linkedin-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server that lets AI assistants like Claude read LinkedIn data through your own logged-in browser session. Access profiles and companies, search for jobs, or get job details.19Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with LinkedIn, including job search, profile viewing, resume/cover letter generation, and application tracking.MIT
- AlicenseAqualityCmaintenanceSelf-hosted, ban-safe MCP server for LinkedIn that provides 22 tools for profiles, search, jobs, posts, connections, and messages. Integrates with any MCP-compatible client like Claude Desktop.581MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to access and interact with LinkedIn data—profiles, messaging, jobs, companies, and more—via MCP, with remote or local deployment.22252 npm9MIT
- AlicenseAqualityCmaintenanceMCP server for LinkedIn that enables AI agents to post, comment, like, and manage content on LinkedIn.104 npm1MIT
- AlicenseNot gradedqualityBmaintenanceA managed MCP server that gives AI agents 160+ typed LinkedIn tools for searching, connecting, messaging, and enriching profiles, with built-in account safety enforcement.13 npm90MIT
TDQS
Scored across 19 tools
Every tool targets a distinct resource and action, from profiles (get_my_profile, get_person_profile) to companies (get_company_profile, get_company_posts) to messaging (get_inbox, send_message). Even potentially overlapping tools like get_feed, get_company_posts, and search_posts are clearly separated by their descriptions, and naming follows a predictable resource-oriented pattern.
All tool names follow a consistent verb_noun snake_case convention: connect_, get_, search_, send_, close_. There is no mixing of camelCase, hyphenation, or inconsistent verb styles. The pattern is immediately understandable and memorable.
At 19 tools, this server sits in the 16-25 range described as heavy. While each tool has a distinct purpose and covers a broad set of LinkedIn features (profiles, companies, jobs, messaging, posts), the count is at the upper edge and feels somewhat overcrowded compared to a typical well-scoped server. Some consolidation, such as folding sidebar profiles into a more general search, could reduce cognitive load.
The server covers a wide range of LinkedIn operations including read access to profiles, companies, jobs, messaging, and feed content, plus write actions like connecting and sending messages. Obvious gaps include the lack of content creation (e.g., posting, commenting) and profile updates, but these are not core to the apparent outreach/job-hunting use case and can be worked around with external tools.