Skip to main content
Glama
AyaanKhan0111

linkedin-discovery-mcp

by AyaanKhan0111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to linkedin-discovery-mcp

No user-submitted related servers found.

    Related Servers

    • LinkedIn MCP Server

      Dev-Anandhan
      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

    • LinkedIn MCP Server

      pauling-ai
      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

    • LinkedIn MCP Server

      damionrashford
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables direct access to LinkedIn through natural conversation, allowing users to search for people, jobs, companies, and groups, as well as view profiles using their existing Chrome browser session.
      11 npm
      -

    • linkedin-mcp-server

      Dishant27
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables LLMs to search for LinkedIn profiles and retrieve detailed profile information via the LinkedIn API, supporting secure OAuth2 authentication.
      85 npm
      52
      MIT

    • LinkedIn MCP Server

      eliasbiondo
      A
      license
      A
      quality
      F
      maintenance
      Enables searching and scraping of LinkedIn for structured data on people, companies, and job listings. It allows AI clients to retrieve detailed profiles, experience, and activity sections using browser automation.
      7
      185
      MIT
    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

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one performs profile searches, the other reports quota status. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow the verb_noun snake_case pattern (search_linkedin_profiles, get_search_quota_status). The naming is consistent and predictable.

    Tool Count3/5

    With only 2 tools, the server is on the thin side. The narrow scope (search + quota) makes it reasonable, but it feels minimal for a discovery-focused server.

    Completeness3/5

    The core search capability is present, but there are notable gaps: no way to fetch a specific profile's details, no explicit pagination, and no advanced filters beyond search criteria. The quota tool is a helpful addition but doesn't round out the surface.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources