Skip to main content
Glama
aarnav-hariramani

LinkedIn MCP Server

by aarnav-hariramani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to LinkedIn MCP Server

No user-submitted related servers found.

    Related Servers

    • linkedin-mcp

      EgiStr
      A
      license
      A
      quality
      B
      maintenance
      Enables LinkedIn API integration for managing profiles, posts, feed, connections, and sending messages through MCP-compatible clients.
      10
      10 npm
      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

      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

    • li-mcp-vercel

      jacobenligne
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing LinkedIn profile and page access via a stateless OAuth proxy, enabling Claude or MCP clients to interact with LinkedIn data.
      -

    • linkedin-mcp

      ml-lubich
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to read and write LinkedIn content through the Voyager API and to use an already logged-in Chrome session for messaging, posting, and referral workflows, with confirmation required before sends or publishes.
      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

    Each tool targets a distinct resource (people, companies, jobs, browser lifecycle), and search vs. detail operations are clearly separated. Minor overlap exists where get_company_profile can fetch posts via sections, duplicating get_company_posts.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: search_*, get_*, send_*, close_*. The naming is predictable and makes the resource and action immediately clear.

    Tool Count5/5

    Eight tools is a well-scoped set for a LinkedIn API covering people, companies, jobs, and connection actions. Each tool serves a distinct purpose without bloat.

    Completeness4/5

    The main workflows are covered: search people, view profiles, send connection requests, search jobs, get job details, and view company info/posts. Minor gaps exist, such as no company search, no connection request with a note, and no direct 'view my profile' tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources