Skip to main content
Glama
IzikStar

linkedin-agent-mcp

by IzikStar

Related Servers

Alternatives to linkedin-agent-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to search and retrieve LinkedIn jobs, profiles, companies, people, posts, reactions, groups, and inbox conversations through typed MCP tools, with safety limits and no browser automation.
      24
      172 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language interaction with LinkedIn, including profile retrieval, job searching, messaging, and post engagement.
      3
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables searching and scraping of LinkedIn profiles, companies, jobs, and posts using natural language through MCP-compatible AI clients.
      13
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with LinkedIn tools and services through the Universal MCP framework, allowing operations like posting and profile management via natural language.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that provides tools to interact with LinkedIn's Feeds and Job API. You can do "search for 3 data engineer jobs in . For each job check if it a good match for me by analyzing it against my resume in file resume.md."
      207
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching public LinkedIn job listings and managing a canonical WeKruit candidate profile, including LinkedIn-based login and resume upload, via command-line and MCP tools.
      MIT

    TDQS

    A4.1/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear READ/PREPARE/EXECUTE labels and local-vs-LinkedIn boundaries. Related pairs like get_action/list_actions and get_application/preview_application are differentiated by singular-vs-list and structured-state-vs-rendered-preview purposes.

    Naming Consistency5/5

    All tools use the same linkedin_ prefix and snake_case convention, mostly following a verb_noun pattern. Minor variations like linkedin_auth_status remain readable and do not break the overall consistency.

    Tool Count3/5

    At 20 tools, the set is on the heavy side and falls into the borderline 16-25 range. While many tools earn their place through the prepare/execute safety model, some pairs could potentially be consolidated.

    Completeness3/5

    Core job search, tracking, job detail, and application preparation are covered. However, execute tools are missing for application submission, message sending, connection request sending, and profile update application, creating notable dead ends for end-to-end workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues