Skip to main content
Glama
Mohamed-Godaa

LinkedIn MCP for OpenWorker

by Mohamed-Godaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to LinkedIn MCP for OpenWorker

No user-submitted related servers found.

    Related Servers

    • linkedin-mcp-server

      sviera91
      A
      license
      A
      quality
      B
      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
      57 npm
      MIT

    • linkedin-mcp-server

      Ramankumar6566
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for LinkedIn API integration. Enables authentication, profile access, connections, search, messaging, and feed management via OAuth2.
      -

    • LinkedIn Poster MCP

      codebytemirza
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets you publish text and image posts to LinkedIn, fetch your profile, and check auth status using natural language.
      MIT

    • SalesTouch

      antoineDsh
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AI-native LinkedIn prospecting. It enables lead research, audience building, conversation management, and controlled outreach actions such as messaging and publishing through an OAuth-protected remote endpoint.
      2
      MIT

    • linkedin-mcp

      KpihX
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for LinkedIn, enabling posting, liking, commenting, and profile retrieval via official OAuth 2.0. Features CLI, HTTP admin, and optional Telegram bot.
      14 npm
      MIT

    • linkedin-mcp-oauth

      zecloud
      A
      license
      Not graded
      quality
      B
      maintenance
      Remote MCP server for LinkedIn hosted on Azure Functions, enabling profile retrieval and post publishing through OAuth.
      57 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 8 tools

    Disambiguation4/5

    Most tools are clearly distinct, but linkedin_start_oauth_flow and linkedin_exchange_authorization_code overlap since the start flow already includes exchanging the authorization code. An agent could be unsure which to use for a given OAuth scenario.

    Naming Consistency5/5

    All tool names follow a consistent linkedin_verb_noun snake_case pattern. Verbs are clear and predictable, making the toolset easy to navigate.

    Tool Count5/5

    Eight tools is well-scoped for a LinkedIn MCP covering authentication, profile access, and post management. Each tool earns its place without unnecessary bloat.

    Completeness4/5

    Core auth and post workflows are covered, but the post surface is read/create only—there is no update or delete post tool. This is a minor gap for typical LinkedIn content management workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources