Skip to main content
Glama
Sign In
linkedin-mcp

linkedin-mcp

by amankumar-2001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to linkedin-mcp

No user-submitted related servers found.

    Related Servers

    • linkedin-mcp

      EgiStr
      A
      license
      A
      quality
      D
      maintenance
      Enables LinkedIn API integration for managing profiles, posts, feed, connections, and sending messages through MCP-compatible clients.
      10
      7 npm
      MIT

    • LinkedIn MCP Server

      aarnav-hariramani
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible clients to read LinkedIn profiles, companies, and jobs, and to send connection requests after explicit confirmation, using interactive browser-based authentication instead of stored credentials.
      8
      MIT

    • linkedin-mcp

      echohello-dev
      A
      license
      A
      quality
      C
      maintenance
      Lets MCP clients sign a member in through LinkedIn's three-legged OAuth flow, read that member's OpenID profile, and publish text posts on their behalf, with stored sessions kept in a local mode-0600 file. It uses only public member APIs, so messaging, invitations, media uploads, and other people's data stay out of scope.
      6
      MIT

    • linkedin-mcp-server

      sviera91
      A
      license
      A
      quality
      D
      maintenance
      Local-first MCP server using LinkedIn's official OAuth and REST APIs to connect a member account, read profile, and publish text posts.
      4
      71 npm
      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

    A3.9/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: auth status, profile retrieval, three post-creation variants by content type, preview, and deletion. The create_text_post/create_link_post/create_image_post split is explicit, and preview_post is clearly differentiated as non-publishing.

    Naming Consistency4/5

    Most tools follow a predictable snake_case verb_noun pattern: get_my_profile, create_text_post, create_link_post, create_image_post, preview_post, delete_post. auth_status is the main deviation, using a noun phrase rather than a verb-led action name.

    Tool Count5/5

    Seven tools is well-scoped for a LinkedIn posting integration. The set avoids redundant tools while covering authentication, profile access, post preview, multiple post types, and deletion.

    Completeness3/5

    Core posting workflows are covered, including preview and delete, but there is no tool to list or retrieve existing posts, and no way to edit or update a post. These are notable gaps for a full LinkedIn post-management surface, though agents can still perform the primary create/delete lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources