Skip to main content
Glama
PeterEkwere

linkedin-mcp

by PeterEkwere
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to linkedin-mcp

No user-submitted related servers found.

    Related Servers

    • linkedin-mcp

      2060-io
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to publish posts, images, comments, and reactions to LinkedIn as the authenticated user, with built-in safety features like daily budgets and deduplication.
      9
      9 npm
      1
      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

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

    • Quillpost

      ApiCartOps
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to build, check and preview LinkedIn posts using seven structured styles, then publish text, images, documents or link cards to the user's own profile through LinkedIn's official API. Also covers drafts, a local schedule and post history, with publishing, deleting and commenting gated behind an explicit approval flag.
      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
      9 npm
      2
      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

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a distinct phase of the action lifecycle (status, prepare, execute, list, cancel) with no overlapping responsibilities. Descriptions explicitly clarify what each does and does not do, making selection unambiguous.

    Naming Consistency4/5

    All tools share the linkedin_ prefix and snake_case, with four following a verb_noun pattern. linkedin_status is a noun-only outlier, but overall naming is consistent and readable.

    Tool Count5/5

    Five tools fully cover the propose-approve-execute-cancel cycle without redundancy. The count is well-scoped for the focused purpose of managing LinkedIn write actions with approval.

    Completeness4/5

    The surface covers preparation, execution, cancellation, listing, and status for write actions. Missing an update/edit action and broader read operations, but the approval workflow itself has no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources