LinkedIn MCP Server
Related Servers
Alternatives to LinkedIn MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceFully featured MCP server that provides automation tools for LinkedIn, supporting browser-based scraping and API-based operations for content management, media uploads, and reactions.63MIT
- AlicenseBqualityCmaintenancePlaywright-powered MCP server for LinkedIn that automates jobs, profile edits, messaging, network actions, and feed posts using a real logged-in browser session.36Apache 2.0
- AlicenseNot gradedqualityAmaintenanceAn MCP server providing generic browser automation and HTTP primitives for operating a LinkedIn session, supporting local Chromium or cloud browsers, with deterministic tools and optional AI tasks.8MIT
- FlicenseAqualityCmaintenanceMCP server for automating LinkedIn actions such as reading feeds, sending messages, creating posts, and managing connections. Uses browser automation with proxy and stealth support.21-
- AlicenseAqualityDmaintenanceHigh-performance autonomous MCP server that turns LinkedIn into an API for AI workflows, enabling profile management, job search, content posting, and document generation.141MIT
- AlicenseAqualityCmaintenanceMCP server for safe LinkedIn automation: official-API posting, comments, and likes plus guest-endpoint job search and a local application tracker.16MIT
TDQS
Scored across 31 tools
Each tool targets a distinct resource/action combination. The prepare/execute pairs are clearly separated by their non-mutating vs mutating roles, and search/get/list tools have well-defined boundaries. No two tools appear to perform the same operation.
All tools follow a consistent 'linkedin.<domain>.<action>' or 'linkedin.<domain>.<subresource>.<action>' pattern with snake_case and standard verbs (get, search, list, prepare, execute). This makes the tool surface predictable and easy to navigate.
31 tools is on the heavy side, but the breadth of LinkedIn's platform (posts, jobs, people, companies, invitations, connections, messaging, plus server metadata) justifies the count. Each tool has a clear purpose, and the prepare/execute pairs account for many of the tools without redundancy.
The set covers the core LinkedIn workflows: reading/searching across major resources, and performing key mutations (create post, comment, react, send/accept/ignore invitations, message). Notable gaps include post deletion/editing and job application, but these are workaround-able for most agent use cases.