leadpipe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUNTER_API_KEY | No | Hunter.io API key for company data enrichment | |
| HUBSPOT_API_KEY | No | HubSpot private app access token for CRM export integration | |
| PIPEDRIVE_API_KEY | No | Pipedrive API key for CRM export integration | |
| GOOGLE_SHEETS_CREDENTIALS | No | Google service account JSON credentials for Google Sheets export |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lead_ingestA | Add a new lead to the pipeline. Provide email (required) and optional fields like name, job title, company. Duplicate emails are rejected. |
| lead_batch_ingestB | Add multiple leads at once (1-100). Returns count of ingested and skipped (duplicates). |
| lead_enrichA | Enrich a lead with company data (industry, size, country, tech stack) using the email domain. Provide the lead ID. |
| lead_scoreA | Calculate an AI-powered qualification score (0-100) for a lead based on job title, company size, industry, and custom rules. Updates the lead status to qualified (>=60) or disqualified (<60). |
| lead_searchB | Search and filter leads by text query, status, score range, source, or tags. Supports pagination. |
| lead_exportB | Export leads to HubSpot, Pipedrive, Google Sheets, CSV, or JSON. Optionally filter by lead IDs or minimum score. |
| pipeline_statsA | Get lead pipeline analytics: total leads, status/source breakdown, average score, score distribution, conversion rates. |
| config_scoringA | View or update the lead scoring configuration. Pass empty object to view current config. Pass fields to update weights, titles, industries, or custom rules. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| recent-leads | The 50 most recently added leads |
| pipeline-overview | Active pipeline summary with lead counts by status |
| scoring-config | Current scoring engine configuration |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/enzoemir1/leadpipe-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server