Skip to main content
Glama
rcreech93

LinkedIn MCP

by rcreech93
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to LinkedIn MCP

No user-submitted related servers found.

    Related Servers

    • linkedin_mcp

      devleads
      F
      license
      A
      quality
      C
      maintenance
      MCP 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
      -

    • LinkedIn MCP Server

      selvin-paul-raj
      A
      license
      A
      quality
      D
      maintenance
      Fully featured MCP server that provides automation tools for LinkedIn, supporting browser-based scraping and API-based operations for content management, media uploads, and reactions.
      6
      3
      MIT

    • linkedin-mcp-server

      Ramankumar6566
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for LinkedIn API integration. Enables authentication, profile access, connections, search, messaging, and feed management via OAuth2.
      -

    • LinkedIn MCP

      Eldasoky1
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for programmable LinkedIn automation via Playwright, offering 20 tools for profile management, messaging, feed interaction, and job searching through real browser automation.
      13 npm
      MIT

    • LinkedIn MCP Server

      markswendsen-code
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for LinkedIn automation that enables users to search for jobs, retrieve profile details, manage connections, and read or send messages. It leverages Playwright and Browserbase to interact with LinkedIn through an existing authenticated browser session.
      6
      6 npm
      1
      MIT
    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

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one extracts a full profile from a URL or username, while the other searches for profiles by name. There is no overlap or ambiguity in their intended use.

    Naming Consistency3/5

    The tool names do not follow a consistent verb_noun pattern. 'linkedin_profile' is a noun phrase, while 'profile_search' places the verb at the end. This is a minor inconsistency, but both names are descriptive and readable.

    Tool Count3/5

    With only 2 tools, the server feels slightly thin for a comprehensive LinkedIn integration. However, the two tools cover the core search-and-retrieve workflow, so the count is borderline appropriate for a focused profile-scraping server.

    Completeness4/5

    The tool set covers the main workflow of finding a profile via search and then retrieving its full details. Missing features like connections or posts are not critical for the apparent purpose of profile extraction, so the coverage is solid with only minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources