How to connect Hunter to Hermes Agent
Connect Hunter to Hermes with ClawLink: paste your Hunter key once and 26 tools work from chat. No MCP server to run, nothing stored on your machine.
HunterAPI KEYMCPFind and verify professional email addresses and leads. Once connected, Hermes Agent can read and act on Hunter from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Hunter access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Hunter setup: pair once in the browser and your always-on Hermes agent can act on Hunter for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
Set up ClawLink for Hermes and tell me when it's ready.
1. Install the plugin:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2. Start pairing. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
3. I'll approve it in my browser, then reply "approved".
4. When I say approved, finish setup:
hermes clawlink finish
5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Hermes to Hunter.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Hunter
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Hunter?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Hunter in the ClawLink dashboard — paste your Hunter API key once.
Verify the connection by asking Hermes:
Run hunter_domain_search for <domain> and show me the email patterns it found, with the count of addresses. Do not contact anyone.
Using a different agent?
The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Hunter is connected in the dashboard, that agent calls the same 26 Hunter tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Hunter MCP for Hermes
Looking for a Hunter MCP server for Hermes Agent? ClawLink connects Hunter to Hermes Agent and exposes 26 Hunter tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Hunter integration works the same way.
This page is about Hunter.io, the email finder, and search results mix it with two other Hunters: Hunter Alpha, the LLM served on OpenRouter, and Hunters, the security platform. Everything below is Hunter.io: domain search, the email finder, the verifier, and enrichment. The connection uses an API key pasted once on the hosted setup page and held server-side, and nothing runs on your machine. That last point matters, because the permission answers search results give for "Hunter Hermes" are about local setups: shell permissions, ~/.zshrc ownership, chmod, and running hermes doctor. None of those apply to a hosted connection, which has no shell, no config file, and no local MCP server to fix.
What the Hermes Agent Hunter integration can do
26 Hunter tools are ready for Hermes Agent once the account is connected. The 23 below are the ones people reach for most; your agent can call all 26.
23 of 26 Hunter tools for Hermes
| Tool | What it does |
|---|---|
Combined enrichment hunter_combined_enrichment | Find person and company info from an email |
Company enrichment hunter_company_enrichment | Get enrichment information for a company |
Create lead hunter_create_lead | Create a new lead |
Create leads list hunter_create_leads_list | Create a new leads list |
Discover companies hunter_discover_companies | Search and retrieve companies matching criteria |
Domain search hunter_domain_search | Search all email addresses for a given domain |
Email finder hunter_email_finder | Find the most likely email address for a person |
Email verifier hunter_email_verifier | Verify the deliverability of an email address |
Account information hunter_account_information | Retrieve information about your Hunter account |
Email count hunter_email_count | Get the total number of email addresses Hunter has for a domain or company with breakdowns by |
Get custom attribute hunter_get_custom_attribute | Retrieve details of a specific custom attribute |
Get lead hunter_get_lead | Retrieve details of a specific lead by ID |
Get leads list hunter_get_leads_list | Retrieve details of a specific leads list by ID |
List campaigns hunter_list_campaigns | Get all email campaigns in your Hunter account |
List custom attributes hunter_list_custom_attributes | List all custom lead attributes in your account |
List leads hunter_list_leads | List all leads saved in your account with optional filters |
List leads lists hunter_list_leads_lists | List all leads lists in your account |
People enrichment hunter_people_enrichment | Find all information associated with an email address or LinkedIn profile including name |
Create custom attribute hunter_create_custom_attribute | Create a new custom lead attribute in your account |
Update custom attribute hunter_update_custom_attribute | Update an existing custom attribute's label |
Update lead hunter_update_lead | Update details of an existing lead by ID |
Update leads list hunter_update_leads_list | Update the name of a specific leads list |
Upsert lead hunter_upsert_lead | Create or update a lead by email in one call |
Try it: find the Hunter tool you need
Browse the 23 Hunter tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Run hunter_domain_search for <domain> and show me the email patterns it found, with the count of addresses. Do not contact anyone.
Run hunter_email_finder for <first> <last> at <company> and show me the address and its confidence score.
Take these addresses and run hunter_email_verifier on each, then tell me which are deliverable and which are risky.
Run hunter_combined_enrichment for <email>, then create the lead with hunter_create_lead in the list <list name>.
How the Hunter tools behave
The tool split that keeps Hunter prompts cheap and within credit.
- Find, verify, and enrich are different costs. Domain search and email finder find addresses, the verifier checks deliverability, and enrichment pulls full person and company records. Each consumes account credits, so say which stage you want rather than "get me everything".
hunter_email_countis the cheap pre-check. It reports how many addresses Hunter has for a domain or company before a search, which avoids burning a search on a domain with nothing.- Leads live in lists.
hunter_create_leads_list,hunter_get_leads_list,hunter_list_leads,hunter_update_leads_list, andhunter_upsert_leadmanage the pipeline; list names are the ids an agent acts on. - Custom attributes are schema you can read.
hunter_list_custom_attributesandhunter_get_custom_attributeshow the fields a lead record carries, which keeps prompts on real fields. hunter_account_informationis the diagnostic. It reads the connected account, which separates a permissions problem from a credit problem in one call.- Speed thresholds and credits return differently. A 403 with a rate message is a speed-threshold violation; a 429 is credit exhaustion. Telling the two apart decides between slowing down and waiting.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Hunter working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Hunter API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Hunter account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Hunter. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Hunter actions to the runtime in a format your agent can reliably use. | 26 tools for Hunter are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Hunter to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Hunter in the browser, and the 26 tools above work from chat. There is no SDK and no config file, and the Hunter key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Hunter
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
Connection succeeds but no tools appear
Reconnect Hunter from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Hunter tools
Hunter tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Hunter call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Hunter returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
Hunter returns 403 "permission denied" while the account shows as connected
Three causes, and the third is the one that distinguishes Hunter. First, resource access: the connected Hunter account's plan and role decide what the tools can reach, and the connection cannot see past them. Second, the placeholder trap: an agent that has not listed anything guesses an id, and placeholder strings are structurally valid, so the call reaches Hunter and comes back as a permissions failure rather than a bad-argument failure; list first with hunter_domain_search or hunter_list_leads, then act on real ids. Third, request rate: Hunter returns 403 for speed-threshold violations, which is Hunter-specific and distinct from 429, which means credit exhaustion. A burst of domain searches from a single agent is exactly the traffic shape that trips the threshold, so slow the agent down rather than reconnecting.
Ask the agent to diagnose it:
Run hunter_account_information and tell me the account the connection acts as. Then quote the exact error from the failed call and whether it came with a rate message. Do not retry the call yet.Hunter returns 429 or the agent stalls on lookups
A 429 from Hunter means credit exhaustion, not permissions: the account's credit allowance is spent. Retrying makes it worse, because the calls keep counting against the window. The fix is to stop lookups, check the account standing with hunter_account_information, and either wait for the reset or plan a smaller batch. The agent should report the 429 and the tool that hit it, so you can decide between waiting and changing plans.
Ask the agent to diagnose it:
Tell me which Hunter tool returned 429 and how many lookups you have made in this session. Run hunter_account_information and report the account standing. Do not make further Hunter calls until I reply.Hunter tools are missing, or one tool name is not found
The taught answers for this are all local: ENABLE_TOOL_SEARCH=true, hyphen-versus-snake_case naming, clearing caches, restarting the client. None apply here. If no Hunter tools appear, the connection or the pairing is incomplete, so confirm the plugin was installed with --enable, that both hermes clawlink begin and hermes clawlink finish ran, and that Hunter shows as connected in the dashboard. If one name fails, it is wrong rather than missing, and the error lists the nearest real tools. Schemas load on demand, so the first Hunter call in a fresh session can arrive before the catalog and needs one retry.
Ask the agent to diagnose it:
List the Hunter tools you actually have available and tell me which one finds an email address for a person. Then use that exact name.API key setup works but results look incomplete
Double-check that the API key for Hunter has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent Hunter integration?
Yes. ClawLink is the fastest way to connect Hermes to Hunter: link your Hunter account once in the browser and Hermes Agent can call the Hunter API through 26 ready-made tools — no custom code or token handling.
How do I connect Hunter to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Hunter in the dashboard and Hermes can use it from the next message — no config files, and the Hunter key you paste is stored server-side instead of in your environment.
How long does it take to connect Hunter to Hermes Agent?
About two minutes. Sign in, click Connect next to Hunter in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Hunter up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Hunter working from chat.
Which Hunter does this page mean?
Hunter.io, the email and lead finding service: find email addresses for a domain, find a person's email, verify deliverability, and enrich companies and people. Not Hunter Alpha, the open LLM on OpenRouter, and not Hunters, the security platform. When a search result about a "Hunter AI agent" talks about a free AI model, it is answering about the wrong product.
What can the agent do with Hunter?
The 26 tools divide cleanly: find emails with hunter_domain_search, hunter_email_finder, and hunter_email_count, verify them with hunter_email_verifier, enrich records with hunter_combined_enrichment, hunter_company_enrichment, and hunter_people_enrichment, and manage leads with hunter_create_lead, leads lists, campaigns, and custom attributes. hunter_account_information reads the account, which is the diagnostic tool.
Do I need to configure anything on my machine?
No. The answers search results give for Hunter tool problems are local-client surgery: fix mcp.json, clear caches, kill processes, set ENABLE_TOOL_SEARCH, chmod shell files. Those apply to a locally hosted MCP server, and this is not one. The only setup is the plugin install, the pairing handshake, and one pasted key.
Is it safe to connect Hunter to an agent?
Hunter holds contact data, and the connection is API-key based, so the honest claim is the storage one: the key is pasted once, held server-side, never shown to the agent, and revocable from the dashboard. The agent sees what your Hunter account can reach, and disconnecting ends its use of the key.
Hermes paired but still can't use Hunter
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
