# 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.

Source: https://elaichi.ai/connectors/hunter/

## Facts

| | |
| --- | --- |
| Application | Hunter |
| Category | Sales Intelligence |
| AI tools | 153 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Hunter is connected

- 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

## Connect Hunter in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Hunter.
2. Optionally set Share with, then press Connect.
3. Paste a Hunter API key. One person generates a token in Hunter and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Hunter tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Hunter MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Hunter MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Hunter tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Hunter through Elaichi

### Find the right email before the first call

Sales. 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.

### Build a target list from one domain

SDR. 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.

### Verify a list before the campaign goes out

Marketing. 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.

### Reach a candidate who is not on job boards

Recruiting. 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.

### See who is spending the Hunter credits

Revenue operations. 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.

### Push new finds straight into the CRM

Partnerships. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Hunter connection?

Yes. One person connects Hunter with the API key, shares the connection with a team in Elaichi, and nobody else ever handles or sees the key. Each teammate still signs in to Elaichi as themselves, so every Hunter lookup in the audit log carries their own name.

### 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.

## All 153 Hunter tools

Every tool below is callable through https://api.elaichi.ai/mcp once Hunter is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Hunter discover** (Create). Find Hunter companies matching a structured filter set. Returns the matching-company object with content-type-specific attributes. This operation is free. Requires a structured filter set.
- **List all Hunter domain searches** (List). Find email addresses and the people behind them for a Hunter-indexed company domain. Returns a list of contacts (each with email, name, position, seniority, department, and confidence) plus the queried domain, organization, and meta block.
- **Hunter domains search** (Search). Search Hunter for email addresses published for a company domain by sending a JSON or form-encoded request body (the POST form is required to use nested location filters). Returns the discovered data: emails with names, positions, and confidence scores alongside the public sources where they were found. The source for this endpoint documents the…
- **List all Hunter email finders** (List). Find a professional email address in Hunter by combining a LinkedIn handle, or by combining a domain or company with a full name (or first and last name). Returns the best matching email and its supporting sources. Supply either a `linkedin_handle` or a domain/company plus a name; `max_duration` optionally controls how long the lookup runs (3-20,…
- **List all Hunter email verifiers** (List). Verify an email address deliverability in Hunter. Returns a verification result wrapped in a `data` field containing the deliverability status and verification checks (a `valid` or `accept_all` result is also auto-saved to leads unless disabled for the account). Required: email.
- **List all Hunter email counts** (List). Get aggregate email-address counts indexed by Hunter for a Hunter domain (or company when the domain is unknown). Returns: total, personal_emails, generic_emails, department, seniority, job_titles. Requires domain.
- **List all Hunter people finds** (List). Enrich a person in Hunter from an email address. Returns the enriched person record (name, position, employer, location, phone number, and related social profiles) under the response's `data` envelope.
- **List all Hunter companies finds** (List). Enrich a company in Hunter from its domain. Returns the enriched company record (industry, size, location, technologies, funding rounds, and social profiles via a generic attributes payload). Required: domain.
- **List all Hunter combined finds** (List). Enrich a person and company in Hunter in a single call from an email address or LinkedIn handle. Returns: person, company.
- **List all Hunter accounts** (List). Get the connected Hunter account's details and usage. Returns the account object containing identity, plan, team, and credit-balance / quota information. No parameters required.
- **Hunter accounts bulk update** (Update). Update Hunter account details. Returns an empty 204 response on success. Source documents no request-body fields beyond authentication.
- **List all Hunter account stats** (List). Get the Hunter account profile summary. Returns the data object with the account identity, plan details, and most used source.
- **List all Hunter usages** (List). Get the Hunter credit usage summary for the authenticated account. Returns the generic resource response for the /usage endpoint — exact fields are defined upstream; consult the Hunter API docs for the field-level breakdown.
- **List all Hunter usage histories** (List). List Hunter credit usage history entries. Returns the data array returned by Hunter (each item is a usage-history record; field details are defined upstream and not enumerable from the Hunter API spec alone).
- **List all Hunter team members** (List). List team members in the Hunter workspace. Returns an array of team member records; individual fields are content-type-specific and defined upstream. No required parameters.
- **List all Hunter connected apps** (List). List the connected apps (third-party integrations such as HubSpot, Pipedrive, Google Sheets, or SMTP/IMAP inboxes) linked to your Hunter account. Returns an array of records, each with id and attribute_mappings.
- **Get single Hunter connected app by ID** (Get). Get a single connected app in Hunter by id, returning the app id and its attribute_mappings — the list of target_field ↔ source_field pairs that map Hunter fields to the integrated CRM's fields. Each mapping also carries direction and conflict_policy when two-way CRM sync is available for the connection. Required: id.
- **Create a Hunter connected app push** (Create). Push Hunter data (such as leads) to the third-party integration behind a connected app in Hunter. The push is queued and runs asynchronously; the call returns a 202 acknowledgment with the request id. 
- **List all Hunter email accounts** (List). List the Hunter email accounts (sending inboxes) connected to the user's account. Returns: id, signature.
- **Get single Hunter email account by ID** (Get). Get a single Hunter email account by id. Returns: id, email, first_name, last_name, sending_status, daily_limit, provider, sender_name, default_account, signature, profile_picture_url, custom_tracking_domain, sending_schedule, warmup. Required: id.
- **Update a Hunter email account by ID** (Update). Replace a Hunter email account by id. Returns: id, email, first_name, last_name, sending_status, daily_limit, provider, sender_name, default_account, signature, profile_picture_url, custom_tracking_domain, sending_schedule, warmup. Required: id.
- **List all Hunter email accounts capacities** (List). List sending-capacity entries for email accounts in Hunter. Returns the data array of capacity records with resource-specific attributes.
- **Get single Hunter email account health report by ID** (Get). Get an email account health report in Hunter. Returns the health report object with resource-specific fields unwrapped from the upstream data envelope. Required: id.
- **Get single Hunter email account usage by ID** (Get). Get an email account usage report from Hunter. Returns the report data including its id and content-type-specific attributes (the upstream response shape is opaque and not enumerated in Hunter's docs). Required: id.
- **Get single Hunter email account warmup report by ID** (Get). Get a Hunter email account warmup report by id. Returns the report envelope including id and the warmup metrics. Required: id.
- **List all Hunter email account sequences** (List). List the Hunter sequences that send from a given email account. Returns each sequence's id, name, owner, recipient count, lifecycle booleans (started, archived, paused), and timestamps. 
- **List all Hunter campaigns** (List). List Hunter campaigns. Returns an array of campaign records under `data`, each carrying at least an `editable` flag that is true only when the API key's user owns the campaign or is a team admin/owner (the condition for adding recipients).
- **Hunter campaigns start** (Start). Start a Hunter campaign so it begins sending real emails to its recipients. Returns the generic response envelope. 
- **List all Hunter campaign recipients** (List). List recipients of a Hunter campaign. Returns the recipients envelope with data.recipients, and a recipient's email is null when they have asked Hunter to delete their address. 
- **Create a Hunter campaign recipient** (Create). Add recipients to a Hunter campaign by email addresses or lead identifiers. Returns the campaign recipients envelope with data.skipped_recipients, each entry carrying the email and the reason it was skipped; the array is null when no address was skipped. 
- **Hunter campaign recipients bulk delete** (Delete). Remove recipients from a Hunter campaign by email addresses or lead identifiers in bulk. For draft campaigns the recipients are removed; for started campaigns their pending emails are canceled. Returns the campaign recipients envelope with data.recipients_removed, data.recipients_canceled, data.messages_canceled, and data.skipped_recipients.…. 
- **Create a Hunter campaign follow up** (Create). Add a follow-up step to a Hunter campaign. Returns the saved follow-up step record including its id and step-specific attributes as defined upstream. 
- **Get single Hunter campaign follow up by ID** (Get). Get a Hunter campaign follow-up step by id. Returns the step record including its id and step-specific attributes as defined upstream. Required: id, campaign_id.
- **List all Hunter sequences** (List). List Hunter outreach sequences in your account. Returns: id, name, editable, started, archived, paused, recipients_count, owner.
- **Create a Hunter sequence** (Create). Create a new Hunter outreach sequence. Returns the created sequence with id, name, editable, lifecycle booleans (started, archived, paused), recipients_count, and owner. Requires ai_assistant_enabled when opted in.
- **Get single Hunter sequence by ID** (Get). Get a Hunter sequence by id, returning its full configuration. Required: id.
- **Update a Hunter sequence by ID** (Update). Replace a Hunter sequence by id (full-config replacement). Sender IDs must be available for outreach to the sequence owner; setting ai_assistant_enabled to true requires a paid AI writing-assistant plan. Required: id.
- **Delete a Hunter sequence by ID** (Delete). Delete a Hunter sequence by id (DRAFT sequences only). Returns an empty 204 response on success. Required: id.
- **Hunter sequences start** (Start). Start a Hunter sequence so it begins sending outbound emails to its recipients. Returns the generic resource envelope (data contains the sequence record). 
- **Hunter sequences pause** (Pause). Pause a started Hunter sequence so it stops sending outbound emails until it is resumed. Returns the generic resource envelope (data contains the sequence record). 
- **Hunter sequences archive** (Archive). Archive a started Hunter sequence to file it once it is finished. Returns the generic resource envelope (data contains the sequence record). 
- **Hunter sequences resume** (Resume). Resume a paused Hunter sequence so it starts sending outbound emails again. Returns the generic resource envelope (data contains the sequence record). 
- **List all Hunter sequence follow ups** (List). List the follow-up steps of a Hunter sequence in step order. Returns each step as a follow-up record with content-type-specific fields wrapped in a generic resource envelope. 
- **Create a Hunter sequence follow up** (Create). Add a new email follow-up step to a Hunter sequence. Returns the created follow-up step record wrapped in a generic resource envelope. 
- **Get single Hunter sequence follow up by ID** (Get). Get a single follow-up step from a Hunter sequence by its follow-up id. Returns the follow-up step record wrapped in a generic resource envelope. Required: sequence_id, id.
- **Update a Hunter sequence follow up by ID** (Update). Replace an existing follow-up step of a Hunter sequence, including possibly the introduction email (step 0). Returns the rewritten follow-up step record wrapped in a generic resource envelope. Required: sequence_id, id.
- **Delete a Hunter sequence follow up by ID** (Delete). Delete a follow-up step from a Hunter sequence. Returns an empty 204 response on success. Required: sequence_id, id.
- **List all Hunter sequence stats** (List). Get performance stats for a Hunter sequence. Returns the sequence's stats object, including its id and the performance metrics tracked for the sequence. 
- **List all Hunter sequence recipients** (List). List recipients of a Hunter sequence. Returns an array of recipient records under `data` (recipient-level fields are documented upstream and not enumerated here). 
- **Create a Hunter sequence recipient** (Create). Add recipients to a Hunter sequence. Returns the created recipient records under `data`, plus `data.skipped_recipients` listing emails and lead_ids that were not added with their `reason` (null when none were skipped). 
- ...and 103 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
