F
licenseNot graded
qualityC
maintenanceEnables AI-powered LinkedIn automation, including content generation, profile and company data extraction, connection requests, and post scraping through MCP tools.
-
linkedin-prospection-mcp
Related Servers
Alternatives to linkedin-prospection-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI-powered LinkedIn content creation, profile and company analytics, lead generation, and connection request automation through MCP tools.-
- FlicenseNot gradedqualityDmaintenanceEnables automated lead generation, AI enrichment, personalized messaging, and outreach orchestration through MCP tools and n8n workflows.-
- AlicenseNot gradedqualityBmaintenanceMCP-native sales intelligence server enabling prospect enrichment, LinkedIn scraping, and CRM push to HubSpot/Salesforce via natural language.81 npmMozilla Public 2.0
- AlicenseNot gradedqualityBmaintenanceMCP 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.2MIT
- AlicenseAqualityDmaintenanceAI client acquisition autopilot. 15 MCP tools for LinkedIn, Email, X, Instagram & Blog outreach from Claude.149 npmMIT
TDQS
A3.9/5.0
Scored across 7 tools
Disambiguation4/5
Tools are generally distinct, though `qualify_leads` and `score_lead` serve similar scoring functions (batch vs. individual). The `personalize_message` tool generates content without sending, which could be confused with messaging actions embedded in `run_pipeline`, but descriptions clarify this adequately.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (find_leads, manage_lead, run_pipeline, etc.). The vocabulary is domain-appropriate and predictable throughout the set.
Tool Count4/5
Seven tools is appropriate for a LinkedIn prospecting domain, falling within the ideal range. Slight redundancy exists between individual (`score_lead`) and batch (`qualify_leads`) scoring operations, but each earns its place for different workflow patterns.
Completeness3/5
Notable gaps exist: no `get_lead` or `list_leads` to read individual pipeline entries, and no standalone `send_invitation` or `send_dm` tool (sending only available through the automated `run_pipeline`). Agents can work around these using `get_pipeline_status` and `run_pipeline`, but granular control is missing.
Maintenance
ActivityInactive
ResponsivenessNo issues