Skip to main content
Glama
nadirzhon

linkedin-mcp

by nadirzhon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to linkedin-mcp

No user-submitted related servers found.

    Related Servers

    • LinkedIn MCP

      nitishnaidi
      A
      license
      A
      quality
      B
      maintenance
      Enables secure LinkedIn OAuth connection and publishing of text and single-image posts with explicit human approval before anything goes live.
      5
      12 npm
      MIT

    • 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
      12 npm
      Apache 2.0

    • writio-mcp-server

      Writio
      A
      license
      Not graded
      quality
      D
      maintenance
      LinkedIn-native AI content creation, scheduling & analytics. Write and post on LinkedIn, create drafts, generate hooks & hashtags, schedule posts, and track engagement — all through natural language.
      34 npm
      MIT

    • LinkedIn Actions MCP

      leandrojacome
      A
      license
      B
      quality
      C
      maintenance
      Enables publishing text or image posts to LinkedIn through the official API and preparing or submitting simplified job applications using a secure local browser session, with user confirmation and privacy safeguards.
      2
      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

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: auth_status checks authorization, publish_now posts immediately, schedule_post queues for later, list_posts retrieves posts, cancel_scheduled removes queued posts, post_brief gives content guidance, and content_calendar provides a posting cadence. No two tools overlap in function.

    Naming Consistency3/5

    Naming mixes verb-first patterns (publish_now, schedule_post, list_posts, cancel_scheduled) with noun-first patterns (auth_status, post_brief, content_calendar). All are snake_case and readable, but the verb/noun order is inconsistent.

    Tool Count5/5

    With 7 tools, the set is well-scoped for a LinkedIn posting server. Each tool earns its place without unnecessary bloat, covering authentication, publishing, scheduling, listing, canceling, and content guidance.

    Completeness4/5

    The core lifecycle is covered: create (publish/schedule), read (list), and delete (cancel scheduled). Missing operations like deleting published posts or editing scheduled posts are minor and can be worked around via cancel-and-recreate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources