Skip to main content
Glama
Romankhanfx01

mcp-server-linkedin

by Romankhanfx01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-server-linkedin

No user-submitted related servers found.

    Related Servers

    • Linked API MCP

      zecloud
      A
      license
      A
      quality
      B
      maintenance
      Connects LinkedIn to AI assistants, enabling lead search, profile analysis, messaging, and workflow automation through a cloud browser. Supports sales, recruiting, and market research tasks.
      59
      251 npm
      MIT

    • LinkedIn MCP Server

      AndresMinakata
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to browse profiles and companies, manage messages and inboxes, and search jobs, posts, and people through a locally logged-in browser session. All actions run on the user's own machine.
      19
      Apache 2.0

    • LinkedIn Intelligence MCP

      southleft
      A
      license
      B
      quality
      D
      maintenance
      Connects Claude Desktop to LinkedIn's data layer for AI-powered networking, enabling profile research, content creation and scheduling, engagement automation, analytics tracking, and messaging through natural language.
      85
      42
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.2/5.0

    Scored across 47 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action (posts, jobs, invitations, messaging, profile, settings), so an agent can generally pick correctly. There is some overlap: connect_with_person claims it can also accept an incoming request, colliding with accept_invitation, and create_post vs create_post_with_image differ only by media attachment, but these are minor and descriptions clarify them.

    Naming Consistency5/5

    Nearly every tool follows a clean verb_noun snake_case pattern (get_company_posts, create_post, delete_post, accept_invitation, search_jobs, update_headline). The few noun-leading outliers like close_session and debug_profile_controls still read as consistent imperative names, so the pattern is predictable throughout.

    Tool Count2/5

    47 tools is very heavy for this surface and well past the 25+ threshold. While the LinkedIn domain is broad, the set is inflated by granular settings tools (list_settings_sections, get_setting, update_setting) and an internal debug_profile_controls that most agents would never need, suggesting the surface could be meaningfully consolidated.

    Completeness4/5

    Coverage is strong across posts, comments/reactions, jobs, invitations/connections, messaging, feed, and profile editing, covering the main write and read lifecycles. Minor gaps remain, such as listing your own connections/followers or retrieving your own authored posts, but these are workable limitations rather than dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources