Skip to main content
Glama
Sign In
linkedin-mcp

linkedin-mcp

by aigamer-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to linkedin-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      12 npm
      MIT

    • linkedin-mcp

      PeterEkwere
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to publish text and link posts, comment, react, and delete posts on LinkedIn through the official OAuth API, with every write gated behind human approval via a two-phase prepare/execute flow. Includes exact-match digests, single-use expiring proposals, daily write caps, and private local token storage with zero third-party dependencies.
      5
      MIT

    • linkedin-mcp

      vlpmedialtd
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to publish text, link, and image posts to a personal LinkedIn profile, as well as comment, react, and delete posts, through the official LinkedIn API.
      9
      15 npm
      2
      MIT

    • linkedin-post-mcp

      Yousef200188
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to create and manage LinkedIn posts via OAuth, including text posts, URL shares, deletions, profile lookup, and company page posting.
      2 npm
      MIT

    • LinkedIn MCP Server

      sandeepramdas
      A
      license
      B
      quality
      C
      maintenance
      Allows AI agents to authenticate with LinkedIn and share posts or links via the Model Context Protocol.
      2
      119 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

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools perform clearly separate operations on different resources: reading the authenticated profile versus publishing a post. There is no realistic way to confuse get_profile with create_post.

    Naming Consistency5/5

    Both names follow the same verb_noun snake_case convention (get_profile, create_post) with unambiguous verbs and resources.

    Tool Count3/5

    Two tools is thin for a LinkedIn integration, which naturally spans profiles, posts, feeds, and connections. It is a reasonable minimal pair but feels under-scoped rather than well-developed.

    Completeness2/5

    The surface only supports reading one's own profile and publishing a text post. There is no way to update the profile, read/list one's posts, delete or edit a post, or interact with others, leaving obvious lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources