Hunter MCP integration for AI agents.
Connect AI agents to Hunter through 18 structured actions, including create leads list, create lead, delete lead, and account information. Review authenticat…
- ACTION CONTRACTS
- 18
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Hunter integration exposes
The Hunter Agent App exposes 18 provider-backed actions for communication and marketing work. Its current contract lets an authorized agent create a new hunter leads list, create a new lead in hunter, and delete an existing hunter lead. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Hunter account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Hunter capabilities.
Showing 12 of 18 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
create_leads_listREADCreate a new Hunter leads list.
INPUTS: name
create_leadWRITECreate a new lead in Hunter.
INPUTS: email / first_name / last_name / position / company
delete_leadHIGH IMPACTDelete an existing Hunter lead.
INPUTS: id
account_informationREVIEWRetrieve information about the authenticated Hunter account.
combined_enrichmentREVIEWRetrieve combined person and company enrichment data from Hunter.
INPUTS: email / linkedin_handle
company_enrichmentREVIEWRetrieve company enrichment data for a domain from Hunter.
INPUTS: domain
discover_companiesREVIEWDiscover companies in Hunter using a natural-language query or filters.
INPUTS: query / limit / offset / filters
domain_searchREADSearch public email addresses for a company domain in Hunter.
INPUTS: domain / company / limit / offset / type
email_countREADCount email addresses available for a company domain in Hunter.
INPUTS: domain / company / type
email_finderREVIEWFind the most likely professional email address for a person in Hunter.
INPUTS: domain / company / full_name / first_name / last_name
email_verifierREVIEWVerify the deliverability of an email address in Hunter.
INPUTS: email
get_leadREADRetrieve a single Hunter lead.
INPUTS: id
INPUT CONTRACTS
Know what the action needs before it runs.
create_leads_list
nameOPTIONAL- The name of the Hunter leads list.
create_lead
emailREQUIRED- The lead email address.
first_nameOPTIONAL- The lead first name.
last_nameOPTIONAL- The lead last name.
positionOPTIONAL- The lead job position.
companyOPTIONAL- The lead company name.
delete_lead
idOPTIONAL- The Hunter resource ID.
combined_enrichment
emailOPTIONAL- The email address used to enrich the person.
linkedin_handleOPTIONAL- The LinkedIn handle used to enrich the person.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Create Leads List
Create a new Hunter leads list. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
create_leads_listControl Create Lead
Create a new lead in Hunter. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_leadVerify with Domain Search
Search public email addresses for a company domain in Hunter. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
domain_searchSAFETY BOUNDARY
Operate Hunter with explicit limits
- Authorize Hunter with API key and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_lead` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Hunter rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Hunter task completed successfully.
CONNECTION MODEL
API key
Hunter API key passed with the X-API-KEY header. Find or create it on your Hunter dashboard API page.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 7
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Hunter.