Skip to main content
Glama
ni-ti-n

LinkedIn MCP Server

by ni-ti-n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to LinkedIn MCP Server

No user-submitted related servers found.

    Related Servers

    • Postoir by Postoir

      Postoirofficial

      Postoir
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible assistants to manage social publishing workflows, including creating drafts, uploading media, scheduling, publishing, and monitoring delivery.
      5 npm
      Apache 2.0
    • @fopost/mcp by fopost

      @fopost/mcpofficial

      fopost
      A
      license
      A
      quality
      B
      maintenance
      Enables managing social media posts, accounts, and AI-powered content features from any MCP client, including scheduling, publishing, analysis, and AI caption generation.
      14
      12 npm
      MIT

    • linkedin-mcp

      Hoyasumii
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables signed-in users to create, edit, and delete their own LinkedIn posts, including text, images, video, documents, or article links, and to list locally tracked posts and check the authenticated account.
      177 npm
      MIT
    • OwlStack MCP by owlstacks

      OwlStack MCPofficial

      owlstacks
      A
      license
      A
      quality
      C
      maintenance
      Manages social media posts, accounts, and AI usage from MCP-aware clients. Supports scheduling, editing, canceling, AI caption generation, and repurposing URLs into platform-optimized content.
      14
      MIT

    • Postiz MCP Server

      oculairmedia
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with the Postiz social media management platform through MCP tools. Supports creating and managing posts, retrieving integrations, and accessing account information through multiple transport protocols.
      2
      -
    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

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: three upload tools split cleanly by media type (image/video/document), and the post operations (create, create_poll, reshare, update, delete) plus comment and get_profile are mutually exclusive in purpose. Descriptions reinforce the boundaries, e.g. noting that create_post takes exactly one media type.

    Naming Consistency5/5

    Every tool follows a uniform linkedin_verb_noun snake_case pattern (upload_video, create_post, create_poll, reshare_post, update_post, delete_post, get_profile). No mixed conventions or vague verbs appear.

    Tool Count5/5

    Ten tools is well-scoped for the domain: uploads, post lifecycle, engagement, and identity lookup each earn their place with no redundancy or filler.

    Completeness4/5

    Post creation lifecycle (create/update/delete), media uploads, polls, reshares, comments, and profile lookup are all covered, forming a coherent surface. Minor gaps remain: no read/list tools for existing posts or comments, and no reaction/like operations, but core publishing workflows are fully achievable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources