Skip to main content
Glama
echohello-dev

linkedin-mcp

by echohello-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to linkedin-mcp

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
      105 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 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

    • linkedin-mcp-server

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

    • 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
    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 6 tools

    Disambiguation4/5

    Each tool has a distinct function: the login/finish_login pair forms a clear two-step flow, and status, logout, profile, and create_post are all sharply separated. The only mild risk is confusion between linkedin_login and linkedin_finish_login, but descriptions disambiguate the sequence.

    Naming Consistency5/5

    All six tools use a consistent linkedin_ prefix with snake_case verb/noun naming (linkedin_login, linkedin_finish_login, linkedin_status, etc.). The convention is predictable throughout.

    Tool Count5/5

    Six tools is well-scoped for an auth-plus-basic-actions server, with each tool earning its place across the session lifecycle and core member operations.

    Completeness4/5

    The auth lifecycle (login, finish, status, logout) plus profile read and post creation covers the core member flow. Minor gaps exist—no post delete/list, no profile update—but the surface is coherent for its apparent scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources