remote-mcp-linkedin
Related Servers
Alternatives to remote-mcp-linkedin
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables fetching detailed LinkedIn profile data by automating a browser session with your LinkedIn cookie to access full profiles.74 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables extraction of comprehensive LinkedIn profile data including experience, education, skills, and contact information through browser automation. Requires manual LinkedIn credentials input and uses anti-detection measures for reliable scraping.5-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to control LinkedIn (profile, network, messaging, publications, jobs) via MCP using a persistent Chrome profile and anti-detection bypass.-
- AlicenseAqualityBmaintenanceEnables AI assistants to read LinkedIn profiles, company pages, jobs, messages, and feed through a user's logged-in browser session.19Apache 2.0
- AlicenseBqualityAmaintenanceEnables MCP agents to drive an already signed-in Chrome or Edge browser through a local extension bridge, controlling existing tabs and opening task-related HTTP(S) tabs without remote debugging or profile copying.23MIT
- AlicenseNot gradedqualityAmaintenanceProvides MCP tools to control real, logged-in Chrome or Brave browser profiles—tabs, navigation, clicks, and typing—with secure profile isolation and no network listener.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one produces a structured dossier, the other returns raw profile sections. There is no ambiguity about which to use for a given task.
Both tools share the 'linkedin_profile_' prefix, but one uses a noun ('dossier') and the other a verb ('get'), which is inconsistent. A consistent verb-noun pattern would be clearer.
With only two tools, the server feels thin for a platform as broad as LinkedIn. However, the tools are well-focused on profile data, so the count is borderline reasonable for that narrow scope.
The server covers only profile retrieval in two formats, missing many common LinkedIn operations like searching, messaging, or managing connections. This is a significant gap for general LinkedIn usage.