Skip to main content
Glama
Jrudani21

linkedin-mcp-server

by Jrudani21
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to linkedin-mcp-server

No user-submitted related servers found.

    Related Servers

    • linkedin-mcp-pro

      horizonbymuneeb
      A
      license
      A
      quality
      C
      maintenance
      Self-hosted, ban-safe MCP server for LinkedIn that provides 22 tools for profiles, search, jobs, posts, connections, and messages. Integrates with any MCP-compatible client like Claude Desktop.
      58
      1
      MIT

    • LinkedIn MCP

      devag7
      A
      license
      A
      quality
      A
      maintenance
      Released 3.0.0: 22 MCP tools, guided offline setup, local stdio, Chrome and manual login. No hosted deployment or job-research brief. Writes need opt-in, reviewed preview and human approval. Unofficial; provider compatibility, first-use cohorts, coordinated erasure and Windows privacy proof remain unverified. No mandatory paid service.
      22
      425 npm
      10
      MIT

    • gtm-api: LinkedIn MCP Server

      gtm-api
      A
      license
      Not graded
      quality
      B
      maintenance
      The LinkedIn API and MCP server for AI agents: search, connect, message and enrich on accounts you own, with limits enforced on our server. 20,000+ LinkedIn accounts run on this stack, and under 1% of them have ever been restricted.
      20 npm
      90
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action, from profiles (get_my_profile, get_person_profile) to companies (get_company_profile, get_company_posts) to messaging (get_inbox, send_message). Even potentially overlapping tools like get_feed, get_company_posts, and search_posts are clearly separated by their descriptions, and naming follows a predictable resource-oriented pattern.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case convention: connect_, get_, search_, send_, close_. There is no mixing of camelCase, hyphenation, or inconsistent verb styles. The pattern is immediately understandable and memorable.

    Tool Count3/5

    At 19 tools, this server sits in the 16-25 range described as heavy. While each tool has a distinct purpose and covers a broad set of LinkedIn features (profiles, companies, jobs, messaging, posts), the count is at the upper edge and feels somewhat overcrowded compared to a typical well-scoped server. Some consolidation, such as folding sidebar profiles into a more general search, could reduce cognitive load.

    Completeness4/5

    The server covers a wide range of LinkedIn operations including read access to profiles, companies, jobs, messaging, and feed content, plus write actions like connecting and sending messages. Obvious gaps include the lack of content creation (e.g., posting, commenting) and profile updates, but these are not core to the apparent outreach/job-hunting use case and can be worked around with external tools.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources