Skip to main content
Glama
Hassan220022

harvestapi-mcp

by Hassan220022

Related Servers

Alternatives to harvestapi-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to access 56 LinkedIn platform and OSINT tools over MCP, including profile, post, messaging, connection, search, feed, and engagement operations plus company discovery, employee scraping, username generation, role classification, org chart building, and email deanonymization. Uses cookie-session authentication with local-harness-only live sessions.
      31 npm
      MIT
    • 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
    • A
      license
      A
      quality
      D
      maintenance
      Fully featured MCP server that provides automation tools for LinkedIn, supporting browser-based scraping and API-based operations for content management, media uploads, and reactions.
      6
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A standalone MCP server that exposes typed LinkedIn capabilities (jobs, people, companies, posts, invitations, messaging) through the visible LinkedIn web UI, enabling workflow automation.
      2
      31
      42 PyPI
      7
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for LinkedIn API integration. Enables authentication, profile access, connections, search, messaging, and feed management via OAuth2.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AI-native LinkedIn prospecting. It enables lead research, audience building, conversation management, and controlled outreach actions such as messaging and publishing through an OAuth-protected remote endpoint.
      2
      MIT

    TDQS

    A3.7/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool targets a distinct LinkedIn resource-action pair, with clear separation between searching and getting entities. Within sub-resources, getters for posts, comments, reactions, and replies are unambiguous.

    Naming Consistency5/5

    All tools follow the harvest_<verb>_<resource> pattern, using only 'get' and 'search' as verbs. Multi-word resources are hyphenated consistently, and there are no mixed naming conventions.

    Tool Count4/5

    25 tools is on the higher end but appropriate for the broad scope of LinkedIn entities covered (ads, companies, groups, jobs, leads, posts, profiles, services, and account info). Each tool adds a distinct capability.

    Completeness4/5

    The read-only harvesting scope is well covered, with both search and get operations for most entities. Minor gaps include the absence of get_lead and get_service endpoints, but search results likely satisfy most needs.

    Maintenance

    ActivityStale
    ResponsivenessNo issues