Skip to main content
Glama
LinkedIn MCP

LinkedIn MCP

Related Servers

Alternatives to LinkedIn MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables ChatGPT to connect to LinkedIn via OAuth and perform authorized actions like posting, commenting, replying, and analyzing profile/content with user approval.
      MIT
    • 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
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to read the signed-in member's basic LinkedIn profile details and publish text posts to their feed through LinkedIn's official OAuth 2.0 API, using locally stored credentials.
      2
      18 npm
      MIT
    • 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
    • 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

    TDQS

    B3.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Tools map cleanly to distinct steps: the three OAuth tools (status/start/exchange) are sequential and separable, and get_my_posts vs get_post vs delete_approved_post are clearly differentiated. Minor overlap between linkedin_connection_status and linkedin_capabilities_and_limits, and between the two 'draft' tools, but descriptions make the boundaries clear.

    Naming Consistency4/5

    Every name uses the linkedin_ prefix with snake_case and mostly verb_noun structure (start_oauth, exchange_code, get_my_profile, prepare_post, publish_approved_post). A couple of names are noun phrases (connection_status, capabilities_and_limits), a small but readable deviation.

    Tool Count5/5

    11 tools is well within the ideal range and each earns its place: three auth steps, profile read/draft, and a full post draft-publish-read-delete lifecycle. No filler or redundant tools.

    Completeness3/5

    Auth, profile read, and the post lifecycle are covered, but linkedin_draft_profile_changes is a dead end with no corresponding apply/publish tool, and there is no token refresh, revoke/logout, or engagement (comment/reaction) surface. Some gaps are attributable to documented LinkedIn API restrictions, but agents still hit walls.