Skip to main content
Glama
vlpmedialtd

linkedin-mcp

by vlpmedialtd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to linkedin-mcp

No user-submitted related servers found.

    Related Servers

    • linkedin-post-mcp

      Yousef200188
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to create and manage LinkedIn posts via OAuth, including text posts, URL shares, deletions, profile lookup, and company page posting.
      -

    • LinkedIn MCP Server

      himanshu31shr
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents with read/write access to LinkedIn API, including profile, posts, media, organizations, comments, reactions, and analytics.
      20
      10 npm
      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

    • 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
    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.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair: profile, post CRUD, organization listing, commenting, reacting, and stats. There is no overlap between getting a single post vs. listing posts, and comment/react/stats are clearly separate operations. The descriptions further clarify any potential boundary (e.g., get_post vs. list_posts).

    Naming Consistency5/5

    All tools follow the same linkedin_<verb>_<noun> pattern with snake_case throughout. Each name starts with the domain prefix and then uses a clear action verb (get, create, delete, list, comment, react). Even the phrasal verbs like comment_on_post and react_to_post are internally consistent.

    Tool Count5/5

    The 9 tools are well-scoped for a LinkedIn social API surface. The count covers profile verification, post management, engagement actions, and stats without being bloated. It sits comfortably in the ideal 3–15 range.

    Completeness4/5

    The tool set covers the core social workflow: create/read/delete posts, comment, react, and fetch stats. Missing operations like updating a post or listing individual comments/reactions are minor since LinkedIn edits are limited and stats provide summaries. No major dead ends exist for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources