Skip to main content
Glama

Related Servers

Alternatives to HeyLead

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      LinkedIn from the user's own logged-in Chrome session for AI agents: search, profiles, post engagers, company employees, lists, sequences, inbox and a Research Pack, with hard caps and a human approval queue. Local-first, no headless browser.
      10
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Connects AI assistants like Claude to LinkedIn through your own logged-in browser session, enabling profile and company lookups, messaging, inbox management, job searches, and related actions. All browser interactions run locally on your machine.
      47
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to LinkedIn outreach, enabling lead finding, campaign management, messaging, and analytics through natural language.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables sending LinkedIn messages and invitations, reading conversations, and managing outreach through natural language by automating a real LinkedIn session via a Chrome extension.
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables self-driving LinkedIn prospecting from AI assistants, including finding leads, warming them up, inviting them, and opening conversations, with human approval required before any message is sent.
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      LinkedIn prospect intelligence inside Claude. It automates the research behind outreach, not the sending: scrapes posts, profiles and comment threads into a local SQLite database, classifies what a person or company actually posts about, mines comment threads for people already describing your problem, and surfaces uncommon commonalities worth opening with.
      18
      32
      MIT

    TDQS

    A3.9/5.0

    Scored across 22 tools

    Disambiguation3/5

    Descriptions explicitly cross-reference sibling tools and clarify most boundaries, but several pairs still overlap: account vs accounts, send_message vs answer_inbox for replying, and status/reporting tools such as show_status, analytics, campaign_status, and scheduler_status. The detailed descriptions reduce misselection, but the set has real overlapping purposes.

    Naming Consistency3/5

    All names use snake_case and remain readable, but conventions are mixed: noun-only tools (campaign, prospect, inbox), noun_status tools (campaign_status, scheduler_status), and verb_noun tools (update_contact, create_campaign, send_message). Singular/plural pairs like account vs accounts also weaken predictability.

    Tool Count3/5

    22 tools is borderline heavy for this domain. Many read/status tools could be consolidated, and some messaging tools overlap, so the set feels broader than tightly scoped even though the platform is complex.

    Completeness4/5

    The surface covers the main LinkedIn outreach lifecycle: setup, accounts, ICP generation, campaign creation/editing/control, prospects, contacts, inbox, sending, replies, scheduler, analytics, and meeting booking. Minor gaps exist, such as no dedicated contact creation/deletion or explicit list_campaigns, but agents can generally work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues