Prospect MCP

MCP server for lead enrichment and sales signals. Powered by EnrichLayer for enrichment, Apify for signals.

What It Does

| Capability | Description | |------------|-------------| | Person Enrichment | Full profiles from email, LinkedIn URL, or username | | Company Intelligence | Firmographics, employees, job listings | | Sales Signals | Job changes, funding, hiring, news (via Apify) | | Email Tools | Find and verify email addresses |

Tools (14 total)

Person

| Tool | Description | |------|-------------| | person_enrich | Enrich from email/URL/username (auto-detected) | | person_enrich_many | Batch person enrichment | | person_email_find | Find email from name + domain |

Company

| Tool | Description | |------|-------------| | company_enrich | Firmographics from domain or name | | company_employees_find | Find people at a company | | company_tech_stack | Detect technologies (requires Apify) |

Signals

| Tool | Description | |------|-------------| | signal_job_changes | People who recently changed roles | | signal_funding | Companies that raised funding | | signal_hiring | Companies hiring for specific roles | | signal_news | Recent company news | | signal_tech_adoption | Companies adopting specific tech |

Email

| Tool | Description | |------|-------------| | email_verify | Check if email is deliverable | | email_verify_many | Batch email verification |

Admin

| Tool | Description | |------|-------------| | admin_credits | Check usage and credits |

Setup

1. Get API Keys

• ENRICHLAYER_API_KEY (required) - EnrichLayer
• APIFY_API_KEY (optional) - Apify for signals

2. Add to MCP Config

{
  "mcpServers": {
    "prospect": {
      "command": "npx",
      "args": ["-y", "prospect-mcp"],
      "env": {
        "ENRICHLAYER_API_KEY": "your-enrichlayer-key",
        "APIFY_API_KEY": "your-apify-key"
      }
    }
  }
}

Auto-Detection

The person_enrich tool automatically detects identifier type:

| Input | Detection | |-------|-----------| | [email protected] | Email → /profile/resolve/email | | https://linkedin.com/in/johndoe | LinkedIn URL → /profile | | https://twitter.com/johndoe | Twitter URL | | https://github.com/johndoe | GitHub URL | | johndoe | LinkedIn username (assumed) |

Example Usage

"Enrich [email protected]"
→ person_enrich { identifier: "[email protected]" }

"Find the VP of Sales at stripe.com"
→ company_employees_find { domain: "stripe.com", title: "VP Sales" }

"Find email for John Doe at acme.com"
→ person_email_find { firstName: "John", lastName: "Doe", domain: "acme.com" }

"Show me companies hiring ML engineers"
→ signal_hiring { roles: ["ML Engineer", "Machine Learning"] }

"Check my remaining credits"
→ admin_credits {}

EnrichLayer API

This MCP wraps the EnrichLayer API:

| Endpoint | Tool | |----------|------| | /profile | person_enrich (LinkedIn) | | /profile/resolve/email | person_enrich (email) | | /profile/email | person_email_find | | /company | company_enrich | | /company/employees | company_employees_find | | /company/job | signal_hiring | | /disposable-email | email_verify | | /credit-balance | admin_credits |

Development

# Install
npm install

# Build
npm run build

# Test
npm test

# Run locally
ENRICHLAYER_API_KEY=xxx npm start

Configuration

| Variable | Required | Description | |----------|----------|-------------| | ENRICHLAYER_API_KEY | Yes | EnrichLayer API key | | ENRICHLAYER_API_URL | No | Custom API endpoint | | APIFY_API_KEY | No | Apify key for signals |

License

MIT