Skip to main content
Glama
felipfr

LinkedIn MCP Server

by felipfr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to LinkedIn MCP Server

No user-submitted related servers found.

    Related Servers

    • LinkedIn MCP

      devag7
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to access and interact with LinkedIn data—profiles, messaging, jobs, companies, and more—via MCP, with remote or local deployment.
      2
      22
      85 npm
      10
      MIT

    • LinkedIn Agent MCP

      iushv
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to connect to LinkedIn, accessing profiles and companies, searching for jobs and people, managing saved jobs, updating job-search profile settings, and inspecting analytics.
      1
      Apache 2.0

    • linkedin-mcp

      AriOliv
      A
      license
      A
      quality
      C
      maintenance
      An unofficial Model Context Protocol server enabling AI assistants to access LinkedIn profile data, network connections, search people and jobs, and send messages via OAuth 2.1.
      7
      MIT

    • LinkedIn Sales & Navigator MCP

      adityaidev
      F
      license
      A
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with LinkedIn and LinkedIn Sales Navigator for searching profiles, managing leads, and handling messaging via cookie-based authentication. It supports professional networking tasks such as sending connection requests and retrieving account details through the Model Context Protocol.
      22
      1
      -

    • LinkedIn MCP Server

      baptitse-jn
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server that enables AI assistants to interact with LinkedIn APIs for profile management, content creation, networking, messaging, and analytics.
      2
      -
    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

    B3.2/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is slight overlap between get_my_profile and get_profile, and between get_company_info and get_company_profile. These are minor and descriptions help.

    Naming Consistency5/5

    All tools use a consistent snake_case verb_noun pattern (e.g., accept_connection_request, search_jobs). No mixed conventions or unclear names.

    Tool Count2/5

    At 28 tools, the count exceeds the 25+ threshold for 'too many' per the rubric. While each tool has a clear role, the server would benefit from consolidation or pruning.

    Completeness3/5

    Covers many core LinkedIn actions (search, post, message, connect), but lacks update/delete for posts, profile editing, and connection management beyond accept. Notable gaps for a full-lifecycle tool.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources