linkedin-sales-nav-mcp
Related Servers
Alternatives to linkedin-sales-nav-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to search leads, view profiles, manage lists, send InMails, and export data by automating LinkedIn Sales Navigator through a logged-in browser session.76 npmMIT
- AlicenseAqualityAmaintenanceEnables AI assistants to search leads, view profiles, manage lists, send InMails, and export data from LinkedIn Sales Navigator through browser automation.86 npm15MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to interact with LinkedIn by scraping profiles, companies, job postings, and getting personalized job recommendations using authenticated browser automation.178,301 PyPI4,093Apache 2.0
- AlicenseAqualityCmaintenanceConnects LinkedIn to AI assistants, enabling lead search, profile analysis, messaging, and workflow automation through a cloud browser. Supports sales, recruiting, and market research tasks.59613 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to use an existing browser session to read profiles and companies, search jobs and people, and manage messages and connection requests on LinkedIn.21Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI assistants to access LinkedIn data through the user's logged-in browser session, supporting profiles, companies, job searches, messaging, and feed/posts.21Apache 2.0
TDQS
Scored across 16 tools
Most tools target clearly distinct functions: search, results retrieval, enrichment, messaging, and monitoring are well separated. A few pairs like fetch_lead_profiles/get_lead_profile and enrich_leads/fetch_lead_profiles require reading descriptions to avoid confusion, but the detailed docs resolve the boundaries.
Names are consistently snake_case and mostly follow a verb_noun pattern (search_contacts, export_results, send_message, check_replies). A few noun-style names like outreach_status, next_outreach_batch, and pipeline_status break the pattern, but the overall style remains predictable and readable.
At 16 tools, the set is slightly above the ideal range but still justified by the end-to-end Sales Navigator workflow: search, storage, enrichment, messaging, reconciliation, and pipeline visibility. Each tool serves a distinct need, though the count feels a bit heavy for a single server.
The core lifecycle is well covered: search leads/accounts, retrieve and export results, enrich, profile, select, draft, send, reconcile, and check replies. Notable gaps are the lack of a follow-up send path (only first messages appear supported) and no explicit campaign or query lifecycle management tools.