Skip to main content
Glama
himanshu31shr

LinkedIn MCP Server

by himanshu31shr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to LinkedIn MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • LinkedIn MCP Server

      quinnjr
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to manage LinkedIn profiles, posts, connections, skills, education, and certifications through the LinkedIn API.
      18
      176 npm
      64
      MIT

    • LinkedIn MCP Server

      ASISaga
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with LinkedIn using the official API for profile access, company management, and job postings.
      Apache 2.0

    • ProfileCraft Agent MCP Server

      naifuliang
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to audit professional profiles, check policy compliance, preview posts, and publish explicitly confirmed text posts through LinkedIn's official API.
      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.2/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: post creation is split by content type, reactions, comments, profile info, and organization analytics are separate. No overlapping functionality.

    Naming Consistency4/5

    Most tools follow verb_noun pattern, but there is minor inconsistency: 'add_reaction' vs 'create_comment', and deletion tools are not parallel (delete_post vs delete_org_post). Overall, the pattern is predictable.

    Tool Count5/5

    20 tools cover a broad range of LinkedIn operations without feeling excessive. Each tool has a specific role, and the count is appropriate for the server's scope.

    Completeness2/5

    Significant gaps exist: no tools to retrieve the user's own posts, list a feed, or view reactions. CRUD is incomplete for posts (no read) and reactions (no get). Agents would struggle to perform common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources