Find and verify email addresses, segment and enrich leads, then send outreach sequences by connecting Hunter’s MCP to your LLM.
Works in claude.ai and the Claude apps.
Add Hunter as a custom connector in a few clicks.
On Claude Team and Enterprise plans, only owners (and Enterprise roles with that permission) can add a custom connector. If you’re a member, ask an owner to add Hunter, then connect to it.
Works in ChatGPT on the web.
Add Hunter’s MCP manually using the steps below.
Hunter
https://mcp.hunter.io/mcp
OAuth
Custom MCP servers need ChatGPT on the web and a Business, Enterprise, or Edu workspace. On another plan, use Hunter’s ChatGPT app instead.
Works in GrokBot on the web and in the app.
Add Hunter’s plugin, then connect it with your API key.
Works in the Codex CLI and the Codex IDE extension.
Add Hunter’s MCP from your terminal.
Add Hunter’s plugin, then connect it with your API key.
Works with any MCP-compatible client.
Add Hunter’s MCP to its configuration file.
HUNTER_API_KEY to your Hunter API key, then restart your AI client.
Trusted by thousands of companies
adopting AI for lead generation
Ask an LLM for an email address and it happily invents one that is destined to bounce. Hunter’s Model Context Protocol (MCP) fixes that.
The Hunter MCP is free. All you need is a Hunter account, and your agent spends credits the same way you would in the app.
Connect Hunter to your AIOur MCP server gives your AI agent full access to the Hunter platform: verified B2B email data with the public source on every record, plus the tools to run email campaigns at volume, available whenever you chat with your agent.
“Send a follow-up sequence to last quarter’s closed-lost” becomes a chain of specific actions the agent takes inside Hunter.
Send a follow-up sequence to last quarter’s closed-lost list, but verify the addresses first.
Your “Closed-lost · Q3” list has 24 leads. I verified every address first: 21 came back valid, so I added them to a new three-email sequence, “Q3 closed-lost check-in”, sending from sam@example.com over 10 days. It started once you approved it.
I left out these 3 addresses, which didn’t come back valid:
Find the engineering managers at these 20 companies, and save them to a list called Q4 hiring.
I searched all 20 companies and found 23 engineering managers at 17 of them; the other 3 had no one with that title in Hunter’s data. I saved all 23 to your new “Q4 hiring” list, and each email address has a confidence score of 90% or higher.
A few of the managers now in Q4 hiring:
Who covers fintech at Ledgerline, The Margin, and Fieldnote? Verified email only.
Alex Morgan covers fintech at Ledgerline; Jordan Ellis and Taylor Chen cover banking, fintech, and crypto at The Margin; and Samira Patel is Fieldnote’s dedicated fintech reporter.
Here’s how to reach them:
Which of my sending accounts are running sequences, and which have room for more?
Three of your four accounts are running sequences. alex@example.com and jordan@example.com have room for more: Alex has a light queue and Jordan isn’t sending anything yet. sam@example.com has about 7 sending days of email queued, and taylor@example.com is still warming up, so hold new sequences on both.
Account by account:
You connect the MCP to your agent, and it finds the right tools and data for what you’re building. No more guesswork.
Returned an email address
Ended with a valid email address
Invalid addresses returned
The remote MCP server works with any MCP-compatible client.
Add it once and start prospecting.
Works in claude.ai and the Claude apps.
Add Hunter as a custom connector in a few clicks.
On Claude Team and Enterprise plans, only owners (and Enterprise roles with that permission) can add a custom connector. If you’re a member, ask an owner to add Hunter, then connect to it.
Works in ChatGPT on the web.
Add Hunter’s MCP manually using the steps below.
Hunter
https://mcp.hunter.io/mcp
OAuth
Custom MCP servers need ChatGPT on the web and a Business, Enterprise, or Edu workspace. On another plan, use Hunter’s ChatGPT app instead.
Works in GrokBot on the web and in the app.
Add Hunter’s plugin, then connect it with your API key.
Works in the Codex CLI and the Codex IDE extension.
Add Hunter’s MCP from your terminal.
Add Hunter’s plugin, then connect it with your API key.
Works with any MCP-compatible client.
Add Hunter’s MCP to its configuration file.
HUNTER_API_KEY to your Hunter API key, then restart your AI client.
Here’s a CSV of 200 contacts. Verify each address with Hunter, drop anything invalid or risky, and save the valid ones to a new leads list called Q4 re-engagement.
I have a call with {{company_name}} tomorrow. Use Hunter to pull the contacts there, identify the most senior people in {{department}}, and return names, titles, and verified email addresses.
Find the editors and staff writers at {{publication}} who cover {{topic}}, verify their email addresses, save them to a list called Guest posts, and draft a 2-step pitch sequence for my review.
I need to reach the person responsible for {{function_or_decision}} at {{company_name}}. Search Hunter for contacts at this company, identify the most likely decision-maker based on job title, verify their email address, and draft a short cold email referencing {{context_or_reason_for_reaching_out}}. Keep the email under 100 words and avoid generic openers.
Find everyone working at {{company_name}} in {{department}} roles. Organize them by seniority (leadership, mid-level, individual contributors) and include their verified email addresses where available. Highlight anyone whose title suggests they joined recently or were recently promoted.
I want to run an outreach campaign targeting {{ideal_customer_profile}}. Step 1: find {{number}} matching companies. Step 2: identify and verify contacts in {{job_titles}} roles at each. Step 3: save the verified contacts to a new Hunter leads list called “{{campaign_name}}”. Step 4: add them to a sequence in Hunter with the subject line “{{subject_line}}”. I’ll write the body myself. Confirm each step before moving to the next.
50 credits/month. No card needed.
If you can’t find the answer to your question here, visit the dedicated section in our Help Center.
Visit the Help CenterIt’s Hunter’s official implementation of the Model Context Protocol: a hosted server at mcp.hunter.io/mcp that exposes Hunter’s email finding, email verification, company and people search, enrichment, leads, and sequences as tools any MCP client can call. It runs against your own Hunter account.
Yes. The verification tool checks any address for deliverability and returns a status, and it works alongside the finding and enrichment tools so an agent can find, verify, and save in one pass. Verification costs 0.5 credit (one verification on Data Platform plans) and is free when Hunter can’t reach a verdict.
Any MCP-compatible client: Claude, ChatGPT, Gemini, Perplexity, Cursor, VS Code, Codex, Windsurf, n8n, and agents you build. Config snippets for the coding tools are above. See Hunter for AI & Agents for the full picture.
No. In Hunter’s study of leading models, 76% of the email addresses they produced were invalid: when a model can’t find an address it makes one up. Through the MCP, your agent gets addresses Hunter has found and verified, and when Hunter can’t confirm one, the agent says so instead of guessing.
Yes. The MCP reaches the same records through a different door. Discover, the Domain Search, the Email Finder, the Email Verifier, enrichment, Leads, and Sequences all work through it, within your plan (Data Platform plans don’t include Discover or Sequences), and anything the agent saves appears in the app right away.
No. For a few lookups, the Hunter web app or the Chrome extension is quicker than connecting anything. The MCP earns its two-minute setup when an assistant or agent is doing the work for you: building lists, verifying them, saving leads, and preparing sequences in one conversation.
No paid plan needed. The MCP works on every plan, including Free. Actions use the same credits as the app: 1 credit per email address found, 0.5 per verification, 0.2 per enrichment, and company search is free. On Data Platform plans, each search or verification uses one credit from its own balance (see pricing). You’re never charged when Hunter can’t find or verify an address, and repeating a lookup within the same billing month costs nothing.
On the API keys page of your Hunter account. Config-file clients pass it as X-API-Key on every request. You can create several keys and revoke any of them there. Claude and ChatGPT connect with OAuth and don’t need it; GrokBot and Cursor ask for it during setup.
Start a fresh chat: connections aren’t picked up mid-conversation. Then check that you finished the authorization step, that your account is active, and that your AI plan supports connectors. Still stuck? The Help Center has a checklist per client.
Same data, different interface. The MCP is for AI clients that call tools in natural language. The REST API is for code: products, scripts, and custom agents that make HTTP requests. Both use the same account and credits.
A native connector is Hunter listed inside one assistant, so you add it with a click, but it can expose fewer tools: the ChatGPT app, for example, has no Email Finder, Domain Search, or person enrichment. The MCP works everywhere and gives your agent the full toolset. Browse the available connectors if you’d rather start there.
Yes. This is Hunter’s official MCP server. It only accesses your Hunter data within the permissions you grant, over HTTPS, validates your credential on every request, and never stores it.