Skip to main content
Glama
eliasbiondo

LinkedIn MCP Server

by eliasbiondo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to LinkedIn MCP Server

No user-submitted related servers found.

    Related Servers

    • LinkedIn MCP Server

      Dev-Anandhan
      A
      license
      A
      quality
      D
      maintenance
      Enables searching and scraping of LinkedIn profiles, companies, jobs, and posts using natural language through MCP-compatible AI clients.
      13
      MIT

    • linkedin-mcp-server

      Dishant27
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables LLMs to search for LinkedIn profiles and retrieve detailed profile information via the LinkedIn API, supporting secure OAuth2 authentication.
      82 npm
      52
      MIT

    • LinkedIn Job Scraper MCP

      Anjani27
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search, filter, and extract job listings from LinkedIn using an automated headless browser with semantic AI filtering and deduplication.
      9 npm
      MIT

    • LinkedIn MCP Server

      Sabari2005
      A
      license
      A
      quality
      B
      maintenance
      Lets an AI assistant operate LinkedIn through an authenticated browser session, enabling profile management, posting, networking, messaging, job search, and automated applications.
      100
      56 npm
      1
      MIT

    • Linked API MCP

      zecloud
      A
      license
      A
      quality
      B
      maintenance
      Connects LinkedIn to AI assistants, enabling lead search, profile analysis, messaging, and workflow automation through a cloud browser. Supports sales, recruiting, and market research tasks.
      59
      194 npm
      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

    A3.9/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific LinkedIn resources: company profiles/posts, person profiles, job details/searches, and browser management. There is no overlap in functionality, with clear boundaries between company, person, and job operations.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case (e.g., get_company_profile, search_jobs, close_browser). The naming is predictable and readable throughout the set, using appropriate verbs like 'get', 'search', and 'close'.

    Tool Count5/5

    With 7 tools, this server is well-scoped for LinkedIn data access, covering key entities (companies, people, jobs) and essential operations (profiles, posts, searches, details). Each tool earns its place without being overwhelming or insufficient.

    Completeness4/5

    The toolset provides strong coverage for reading LinkedIn data, including profiles, posts, and jobs with search capabilities. Minor gaps exist, such as no tools for creating or interacting with content (e.g., posting updates or sending messages), but core data retrieval workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources