Hunter MCP connector
Connect Hunter to Elaichi and Claude, ChatGPT, Cursor and Microsoft Copilot can find, verify and count email addresses at any domain, with every lookup logged against the person who asked.
- Connects with an API key
- Free 14-day trial
- No credit card
Find the email for the head of sales at acme.com
Working in Hunter with Elaichi
- List all Hunter domain searches
- Hunter domains search
- List all Hunter email finders
How to connect Hunter to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Hunter MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Hunter MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Hunter MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Hunter MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Hunter MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Hunter to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Hunter through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Hunter is logged.
-
Sales
Find the right email before the first call
Ask for the email address of a named person at a company and get it back with a confidence score. The rep works from the answer instead of guessing at name patterns.
-
SDR
Build a target list from one domain
Run a domain search on a company you want to break into and get everyone Hunter knows there, by department and seniority. Pull a combined find for a company and a person in one ask.
-
Marketing
Verify a list before the campaign goes out
Check every address on an event or webinar list and drop the ones that will bounce. Keep sender reputation intact and the email account health report clean.
-
Recruiting
Reach a candidate who is not on job boards
Find the email of an engineer or designer at a competitor and see how many people Hunter has at that company. Email counts tell you whether the whole team is worth approaching.
-
Revenue operations
See who is spending the Hunter credits
Ask for this month's usage and usage history by team member and find out which seats are busy and which are idle. Account stats answer the renewal question before procurement asks it.
-
Partnerships
Push new finds straight into the CRM
Once a company find turns up the right contact, send it through a connected app push so it lands where the deal is tracked. Email account capacities show how much outreach can go out today.
Try asking
- “Find the email for the head of sales at acme.com”
- “Verify these five prospect emails before I send the sequence”
- “How many email finder credits has the SDR team used this month”
What connecting Hunter gets you
6 screens from Elaichi, each doing one job for your Hunter account.
Ask Elaichi to work across your apps.
Find the email for the head of sales at acme.com
Verify these five prospect emails before I send the sequence
How many email finder credits has the SDR team used this month
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Hunter for a contact in plain words.
Type a question, get an answer from live domain searches and email verifiers.
Copy the endpoint
AI apps
One Hunter endpoint for every AI client.
Claude, ChatGPT and Cursor reach Hunter through one governed endpoint, no SDK, no shared API key.
Tool catalog
153 Hunter tools, no custom code to write.
Domain searches, email finders, verifiers and email accounts, ready the moment Hunter connects.
Toolboxes
Every team gets its own Hunter toolbox.
Sales gets email finders, marketing gets domain searches, each scoped to its own team.
Shared connections
Share Hunter access, never the API key.
One person connects Hunter, teammates work through it without ever seeing the credential.
Audit log
Every Hunter lookup names who ran it.
When, who, what happened and which domain or email, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Hunter digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch domain searches
Hunter
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Hunter
Queued
Workflows
A schedule starts Hunter work, not a chat.
New domain searches are fetched, grouped, drafted into a digest, approved, then pushed back to Hunter.
Hunter health
Refreshed 4 minutes ago · every 15 minutes · from the domain searches collection
Domain searches
1,284 ↓ 12%
Email verifiers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Domain searches created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales US 27%
SDR 21%
Marketing 18%
Collections and dashboards
Hunter numbers you never have to ask for.
Four metrics, a 14 day chart of searches and a team breakdown, computed without a model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Hunter
All three can connect Hunter to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Hunter tools | Allow or restrict single Hunter tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Hunter call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Hunter tools for your AI agents
153 tools are ready to call through Elaichi's MCP endpoint the moment you connect Hunter, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Hunter to Claude?
Two steps. In Elaichi, choose Hunter and paste in the API key from your Hunter account, which is the whole sign-in step, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude signs you in through Elaichi and Hunter is ready to use.
Does Hunter work with ChatGPT and Cursor as well as Claude?
Yes. Hunter is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client. The Elaichi Agent uses it too, so there is nothing separate to set up per client.
What can an AI agent actually do with my Hunter data?
With Hunter connected, an agent can find a person's email at a company, verify whether an address will bounce, count how many addresses Hunter has for a domain, and run a full domain search for a target account. It can also report usage and credits by team member, read email account health, and push a find into a connected app. Short, concrete asks such as a name and a domain work better than long paragraphs.
Does connecting Hunter give the AI my whole Hunter account?
No. Every call runs inside the Hunter access of the person who signed in, so an agent sees the searches, credits and email accounts that person could already see. Elaichi can narrow that access with restrictions and roles, and it can never widen it beyond what Hunter itself allows.
Can I stop an agent from changing things in Hunter?
Yes. Restrictions in Elaichi work per action, so you can allow email finding and verifying while restricting bulk account updates or email account changes, set on a role or on one person. A restricted action still appears in Elaichi's tool search flagged as restricted, but no client can run it against Hunter, whatever the prompt says.
What happens to a Hunter connection when someone leaves?
Offboarding that person in Elaichi ends their access to Hunter through every client at once. A shared Hunter connection keeps working for everyone else on the team. If you want Hunter gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Hunter MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Hunter is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Hunter?
Yes. Both let Claude, ChatGPT or Cursor use Hunter. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Hunter call.
How is Elaichi different from Composio for Hunter?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Hunter: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Hunter in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot