Skip to main content
Glama
Jing-yilin

LinkedIn MCP Server

by Jing-yilin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to LinkedIn MCP Server

No user-submitted related servers found.

    Related Servers

    • LinkedIn Data API MCP Server

      BACH-AI-Tools
      A
      license
      C
      quality
      D
      maintenance
      Enables access to comprehensive LinkedIn data, including professional profile details, company information, and social engagement metrics. It supports searching for people, retrieving posts and comments, and fetching detailed experience, skills, and recommendations.
      52
      MIT

    • LinkedIn MCP Server

      pauling-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language interaction with LinkedIn, including profile retrieval, job searching, messaging, and post engagement.
      3
      Apache 2.0

    • LinkedIn Api8 MCP Server

      BACH-AI-Tools
      A
      license
      C
      quality
      D
      maintenance
      Enables access to LinkedIn data including profile enrichment, company information, job searches, post analytics, and social interactions through the LinkedIn Api8 API with comprehensive search and data retrieval capabilities.
      51
      MIT

    • LinkedIn MCP Server

      VasquezRivero92
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to manage LinkedIn profiles, posts, connections, skills, education, certifications, and other professional data through the LinkedIn API.
      19
      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

    B3.4/5.0

    Scored across 17 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific LinkedIn entities (company, group, job, post, profile) and actions (get vs. search). The naming and descriptions make it easy to differentiate between tools like get_post_comments and get_post_reactions, with no overlapping functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with 'get_' for retrieval and 'search_' for search operations, using snake_case throughout. The naming is predictable and systematic across all 17 tools.

    Tool Count4/5

    17 tools is slightly high but reasonable for a comprehensive LinkedIn API covering multiple entity types and actions. It's well-scoped for the domain, though it could be streamlined by grouping related tools.

    Completeness4/5

    The toolset provides strong coverage for retrieving and searching LinkedIn data across key entities (profiles, companies, jobs, posts, groups). Minor gaps exist, such as no update/delete/create operations, but this is typical for a read-only data extraction server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources