HeyLead
Related Servers
Alternatives to HeyLead
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLinkedIn 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.8MIT
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants to LinkedIn outreach, enabling lead finding, campaign management, messaging, and analytics through natural language.MIT
- AlicenseNot gradedqualityCmaintenanceEnables sending LinkedIn messages and invitations, reading conversations, and managing outreach through natural language by automating a real LinkedIn session via a Chrome extension.13 npmMIT
- AlicenseAqualityAmaintenanceLinkedIn 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.1830MIT
- AlicenseNot gradedqualityBmaintenanceAI-powered content generation for LinkedIn outreach, helping sales teams and recruiters craft personalized connection requests, InMails, posts, comments, and multi-touch outreach sequences. It's a content assistant that generates text for human review and manual sending, fully compliant with LinkedIn's Terms of Service.11 npm93 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceLinkedIn-native AI content creation, scheduling & analytics. Write and post on LinkedIn, create drafts, generate hooks & hashtags, schedule posts, and track engagement — all through natural language.22 npmMIT
TDQS
Scored across 35 tools
Several tools have unclear boundaries: check_replies, inbox, and backfill_inbox all deal with reading/responding to LinkedIn messages, while generate_and_send and send_message both send prospect-facing messages. icp, generate_icp, and profile_signals also overlap in targeting analysis. The detailed descriptions help, but an agent could easily select the wrong tool for reply handling or outreach sending.
Tool names are consistently lowercase snake_case, but the pattern is mixed: some use verb_noun (create_campaign, send_message, import_prospects) while many are bare nouns representing resource managers (scheduler, campaign, prospect, analytics, inbox, contacts, network). This is readable and mostly predictable, but not a uniform verb_noun convention throughout.
35 tools is a heavy surface for a single MCP server, well above the 15-tool threshold that typically indicates a well-scoped set. While the server covers many subdomains (campaigns, inbox, signals, CRM, brand, network), so many top-level tools create navigation and selection burden. Several tools also collapse many actions into single entries, making the count feel inflated rather than appropriately granular.
The tool surface covers the full outreach lifecycle: setup, ICP generation, campaign creation/editing/launch/control, message sending, engagement, replies, meeting booking, prospect management, analytics, imports, CRM sync, and signals. Minor gaps exist—such as no dedicated campaign-template editor or calendar availability checker—but agents can work around these.