Skip to main content
Glama
HDHNezherParking-cum-Y638-Intl-Ltd

linkedin-mcp

by HDHNezherParking-cum-Y638-Intl-Ltd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to linkedin-mcp

No user-submitted related servers found.

    Related Servers

    • linkedin-mcp-server

      greg0r1
      A
      license
      A
      quality
      D
      maintenance
      Enables Claude Desktop to manage your LinkedIn profile and company pages, including posting, reading posts, and fetching profile information.
      7
      74 npm
      4
      MIT

    • linkedin-mcp-server

      ihiteshgupta
      A
      license
      A
      quality
      D
      maintenance
      Enables posting content, sharing articles, and managing your LinkedIn profile through Claude using the official LinkedIn API with OAuth 2.0.
      6
      4 npm
      MIT

    • LinkedIn MCP Server

      Sabari2005
      A
      license
      A
      quality
      B
      maintenance
      Lets an AI assistant operate LinkedIn through an authenticated browser session, enabling profile management, posting, networking, messaging, job search, and automated applications.
      100
      56 npm
      1
      MIT

    • linkedin-mcp-server

      abhineet34
      A
      license
      A
      quality
      D
      maintenance
      Post to LinkedIn from Claude — create posts, upload images, edit/delete posts, and manage company pages via natural language. Uses the official LinkedIn REST API with OAuth 2.0.
      9
      74 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 12 tools

    Disambiguation5/5

    Each tool targets a distinct action/resource: authentication, session status, immediate post, scheduled post, queue management, post listing, comment reading/reply, page listing/page post, and feed reading. No two tools overlap in purpose.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (create_post, schedule_post, list_scheduled_posts, cancel_scheduled_post, list_my_posts, read_post_comments, reply_to_comment, list_pages, create_page_post, read_feed). The exceptions are linkedin_login and linkedin_session_status, which use a prefix style that deviates from the rest.

    Tool Count5/5

    12 tools cover the core LinkedIn automation domain—auth, posting (immediate and scheduled), scheduling queue management, comments, pages, and feed—without excess. This is a well-scoped count for the server's purpose.

    Completeness4/5

    The posting lifecycle is well covered (create, schedule, list, cancel), along with comments and page posts. Missing operations like editing or deleting posts are minor gaps; agents can work around them, but they are noteworthy for a complete LinkedIn content management surface.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources