Skip to main content
Glama
alexanderskorokhodov

remote-mcp-linkedin

by alexanderskorokhodov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to remote-mcp-linkedin

No user-submitted related servers found.

    Related Servers

    • LinkedIn MCP Server

      AndresMinakata
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to browse profiles and companies, manage messages and inboxes, and search jobs, posts, and people through a locally logged-in browser session. All actions run on the user's own machine.
      19
      Apache 2.0

    • LinkedIn Scraper MCP Server

      superyuser
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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
      -

    • LinkedIn Agent Toolkit

      PabloIan92
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and developers to safely interact with an authenticated local LinkedIn browser session through the Chrome DevTools Protocol, supporting profile inspection, headline and About updates, project and experience additions, post creation, and screenshots without storing credentials.
      MIT

    • linkedin-mcp-server

      Steph-ux
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control LinkedIn (profile, network, messaging, publications, jobs) via MCP using a persistent Chrome profile and anti-detection bypass.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources