Hunter MCP is an MCP server that gives AI assistants access to Hunter.io's sales intelligence APIs, letting you search for emails, verify addresses, enrich people and companies, discover companies, and manage leads.
Read account plan and current credit usage with account_info.
Search all email addresses for a domain/company with filters like location, seniority, department, job titles, verification status, and decision-maker.
Find the most likely professional email for a person from company/domain or LinkedIn with email_finder.
Verify an email's deliverability, score, SMTP/MX, accept-all, webmail, disposable status, and sources with email_verifier.
Count how many personal or generic emails Hunter has for a domain/company.
Enrich a person, company, or both from an email/LinkedIn/domain, optionally in Clearbit-compatible format.
Discover companies by natural-language query or structured filters (industry, headcount, funding, technology, location, etc.).
Create a single Hunter lead from an email and optional lead fields/list placement with create_lead (the only mutation).
List leads with many filters on identity, company, status, verification, activity, location, custom attributes, and more.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Hunter MCP Find all email addresses on stripe.com and verify the main one"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Hunter.io MCP server. 11 tools cover domain search, email finding and verification, enrichment, company discovery, and lead management.
Claude Code:
claude mcp add hunter -e HUNTER_API_KEY=your-key -- npx -y @scalably-io/hunter-mcpCodex:
codex mcp add hunter --env HUNTER_API_KEY=your-key -- npx -y @scalably-io/hunter-mcpClaude Desktop: download hunter-mcp.mcpb from the latest GitHub release and open it.
Related MCP server: Prospeo MCP Server
Create an API key at hunter.io/api-keys.
create_lead writes to your Hunter leads list and is the only non-read tool; the other 10 tools are read-only.
Tool | What it does |
| Read the Hunter v2 account plan and exact current credit usage, including remaining unified or per-type balances |
| Search Hunter v2 emails for one domain/company with current people, verification, location, job-title, decision-maker, aggregation, and offset filters |
| Find and automatically verify the most likely professional email from a company/domain plus name, or directly from a LinkedIn handle |
| Verify one email address with Hunter v2 and return exact deliverability, score, SMTP/MX, accept-all, webmail, disposable, and source evidence |
| Count Hunter email coverage for a domain/company, optionally limited to personal or generic addresses, without returning addresses |
| Enrich a person from an email address or LinkedIn handle using Hunter v2, optionally in Clearbit-compatible format |
| Enrich a company from its domain using Hunter v2, optionally in Clearbit-compatible format |
| Enrich both a person and their company from one email using Hunter v2, optionally in Clearbit-compatible format |
| Use Hunter Discover v2 to find companies from current natural-language or structured organization, location, industry, headcount, type, year, keyword, technology, and funding filters |
| Create one Hunter lead from a required email and optional current lead fields, list placement, and custom attributes. This is a single-attempt mutation |
| List Hunter leads with current list, identity, company, status, verification, activity/date, location, tag, campaign, user, confidence, custom-attribute, query, and offset filters |
Variable | Required | Purpose |
| yes | Hunter.io API key from hunter.io/api-keys |
| no | Override the Hunter API base URL (default |
| no | Per-request timeout in milliseconds (default 30000) |
| no | Base delay in milliseconds for the GET retry backoff (default 500) |
Every tool returns plain JSON with status (succeeded, partial, no_op), operation, summary, target, result, proof, warnings, recovery. Failures throw a plain error string: <code>: <message> <hint>.
Hunter's per-plan request quotas surface in account_info.
Each release lists the package version, the .mcpb sha256 and the production commit it was derived from in CHANGELOG.md. CI runs the tests and a clean install of the packed tarball on every push.
This server runs locally, on your machine, under your own credentials. It collects no personal data, contains no telemetry, stores nothing persistently, and talks only to the vendor API it wraps. No third party, including Scalably, receives your data. Contact: hello@scalably.io. Canonical copy: https://scalably.io/connector-privacy.html
MIT. Copyright Scalably.
Read the Hunter v2 account plan and exact current credit usage, including remaining unified or per-type balances.
Inputs: no named parameters.
Enrich both a person and their company from one email using Hunter v2, optionally in Clearbit-compatible format.
Inputs: email (required), clearbit_format.
Enrich a company from its domain using Hunter v2, optionally in Clearbit-compatible format.
Inputs: domain (required), clearbit_format.
Create one Hunter lead from a required email and optional current lead fields, list placement, and custom attributes. This is a single-attempt mutation.
Inputs: email (required), notes, source, company, +15 more.
Use Hunter Discover v2 to find companies from current natural-language or structured organization, location, industry, headcount, type, year, keyword, technology, and funding filters.
Inputs: limit, query, offset, funding, +9 more.
Search Hunter v2 emails for one domain/company with current people, verification, location, job-title, decision-maker, aggregation, and offset filters.
Inputs: type, limit, domain, offset, +9 more.
Count Hunter email coverage for a domain/company, optionally limited to personal or generic addresses, without returning addresses.
Inputs: type, domain, company.
Enrich a person from an email address or LinkedIn handle using Hunter v2, optionally in Clearbit-compatible format.
Inputs: email, clearbit_format, linkedin_handle.
Find and automatically verify the most likely professional email from a company/domain plus name, or directly from a LinkedIn handle.
Inputs: domain, company, full_name, last_name, +3 more.
Verify one email address with Hunter v2 and return exact deliverability, score, SMTP/MX, accept-all, webmail, disposable, and source evidence.
Inputs: email (required).
List Hunter leads with current list, identity, company, status, verification, activity/date, location, tag, campaign, user, confidence, custom-attribute, query, and offset filters.
Inputs: email, limit, query, offset, +33 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Scored across 11 tools
Most tools have clearly distinct purposes, such as account_info, list_leads, email_verifier, and the three enrichment variants. The main ambiguity is between domain_search and email_finder, as both can locate emails for a domain, though one is broad search and the other is targeted person lookup.
Tool naming is inconsistent: some use verb_noun (create_lead, list_leads), some use noun_verb (domain_search), some use noun_noun (email_finder, email_count), and one is a bare verb (discover). This mixed pattern makes the tool surface harder to predict.
11 tools is well-scoped for a Hunter MCP server. Each tool covers a meaningful capability of the Hunter API, including account info, lead management, email discovery, verification, enrichment, and company search, without excessive redundancy.
The server covers most of the Hunter domain well, including search, enrichment, verification, and lead creation. However, lead management is incomplete: create_lead and list_leads exist, but there are no update or delete lead tools, leaving an obvious lifecycle gap.
Hunter.io MCP — wraps the Hunter.io email finder & verification API (hunter.io)
Find verified B2B emails and phone numbers; search and enrich people and companies for prospecting.
People, company, job and LinkedIn post data, plus email finding and verification.
Company and contact enrichment: firmographics from a domain or IP, profiles from a work email.
