AI-powered lead qualification engine for MCP. Ingest, enrich, score, and export leads to your CRM.
If you already use Leadpipe, the leadpipe mcp server is the piece that lets your assistant work with it directly. AI-powered lead qualification engine for MCP. Ingest, enrich, score, and export leads to your CRM.
LeadPipe ingests leads from any source, enriches them with company data, scores them 0-100 using configurable AI rules, and exports qualified leads to your CRM — all through the MCP protocol.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
lead_demo_seed — Seed the pipeline with a realistic demo dataset — 14 leads across 5 archetypes (hot decision-makers, warm mid-level, cold junior/small-co, rawlead_qualify — Filter leads against your Ideal Customer Profile before spending any enrichment credits. Uses only locally-available signals — email domain, joblead_ingest — The lead_ingest tool exposed by this serverlead_batch_ingest — Add 1-100 leads at once. Duplicates are automatically skippedlead_enrich — Returns: company name, industry, size, country, tech stack, LinkedIn URLlead_score — Calculate a qualification score (0-100). Leads scoring 60+ are marked qualifiedlead_search — The lead_search tool exposed by this serverlead_export — The lead_export tool exposed by this serverpipeline_stats — Returns: total leads, status/source breakdown, average score, score distribution, qualified rate, leads today/week/monthconfig_scoring — The config_scoring tool exposed by this serverHubSpot — Set the HUBSPOT_API_KEY environment variable with your HubSpot private app access tokenPipedrive — The Pipedrive tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: LEMONSQUEEZY_LICENSE_KEY, HUBSPOT_API_KEY, PIPEDRIVE_API_KEY, HUNTER_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Leadpipe's toolset — lead_demo_seed, lead_qualify, lead_ingest and 9 more — is a fair guide to whether it matches your workflow. It is maintained by enzoemir1; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| lead_demo_seed | Seed the pipeline with a realistic demo dataset — 14 leads across 5 archetypes (hot decision-makers, warm mid-level, cold junior/small-co, raw unenriched, and disqualified) — so every downstream tool returns meaningful o |
| lead_qualify | Filter leads against your Ideal Customer Profile **before** spending any enrichment credits. Uses only locally-available signals — email domain, job title, country, industry, company size, tech stack — so nothing is char |
| lead_ingest | The lead_ingest tool exposed by this server. |
| lead_batch_ingest | Add 1-100 leads at once. Duplicates are automatically skipped. |
| lead_enrich | Returns: company name, industry, size, country, tech stack, LinkedIn URL. |
| lead_score | Calculate a qualification score (0-100). Leads scoring 60+ are marked **qualified**. |
| lead_search | The lead_search tool exposed by this server. |
| lead_export | The lead_export tool exposed by this server. |
| pipeline_stats | Returns: total leads, status/source breakdown, average score, score distribution, qualified rate, leads today/week/month. |
| config_scoring | The config_scoring tool exposed by this server. |
| HubSpot | Set the HUBSPOT_API_KEY environment variable with your HubSpot private app access token. |
| Pipedrive | The Pipedrive tool exposed by this server. |
Add to your MCP client config:
```json
{
"mcpServers": {
"leadpipe": {
"command": "node",
"args": ["path/to/leadpipe-mcp/dist/index.js"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LEMONSQUEEZY_LICENSE_KEY | Credential the server authenticates with. | Yes |
| HUBSPOT_API_KEY | Credential the server authenticates with. | Yes |
| PIPEDRIVE_API_KEY | Credential the server authenticates with. | Yes |
| HUNTER_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.