
Leadpipe Mcp
Score inbound leads against your ICP, enrich contacts, and push qualified records to HubSpot or Pipedrive from the agent.
Overview
io.github.enzoemir1/leadpipe-mcp is a Grow-phase MCP server for ICP-based lead scoring, Hunter.io enrichment, and HubSpot or Pipedrive export.
What is this MCP server?
- ICP filter plus 0–100 lead scoring for prioritization
- Hunter.io enrichment called out in the server description
- Export path to HubSpot and Pipedrive CRMs
- Stdio npm leadpipe-mcp-server at v1.4.0
- Sales pipeline MCP—not generic web scraping or cold-email copywriting alone
- Server schema version 1.4.0
- npm identifier leadpipe-mcp-server with stdio transport
- Documented 0–100 scoring scale and two CRM export targets (HubSpot, Pipedrive)
What problem does it solve?
Raw leads arrive faster than you can research them, so good opportunities sit beside poor fits with no consistent score or CRM record.
Who is it for?
Indie SaaS and service founders who run a small pipeline and want agent-driven qualification before manual outreach.
Skip if: Teams without a defined ICP, without HubSpot/Pipedrive, or that need enterprise ABM orchestration only via native CRM UI.
What do I get? / Deliverables
After install, your agent can filter by ICP, assign 0–100 scores, enrich contacts, and push qualified leads into HubSpot or Pipedrive.
- Scored lead list with 0–100 prioritization
- Enriched contact records where Hunter.io is configured
- CRM-ready exports toward HubSpot or Pipedrive
Recommended MCP Servers
Journey fit
How it compares
Lead scoring and CRM export MCP, not a substitute for legal compliance review of outbound email programs.
Common Questions / FAQ
Who is leadpipe-mcp for?
Solo builders and small sales teams who qualify inbound or list leads and sync results to HubSpot or Pipedrive.
When should I use leadpipe-mcp?
Use it in Grow when ranking new leads, enriching emails via Hunter.io, or cleaning a list before CRM import.
How do I add leadpipe-mcp to my agent?
Install leadpipe-mcp-server from npm, register stdio MCP, then provide Hunter.io and HubSpot or Pipedrive credentials per the repo setup.