How to connect Hunter to OpenClaw
Connect Hunter to OpenClaw 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, OpenClaw can read and act on Hunter from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Hunter access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Hunter setup: install one ClawHub skill, connect Hunter in the browser, and OpenClaw can call real Hunter actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Hunter skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Hunter" (hith3sh/hunter-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/hunter-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Hunter.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Hunter
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Hunter?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Hunter in the ClawLink dashboard — paste your Hunter API key once.
Verify the connection by asking OpenClaw:
Use Hunter to combined enrichment and walk me through the result in plain English.
Using a different agent?
The OpenClaw 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 OpenClaw
Looking for a Hunter MCP server for OpenClaw? ClawLink connects Hunter to OpenClaw and exposes 26 Hunter tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Hunter integration works the same way.
What the OpenClaw Hunter integration can do
26 Hunter tools are ready for OpenClaw 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 OpenClaw
| 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 OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Hunter to combined enrichment and walk me through the result in plain English.
Use Hunter to company enrichment and walk me through the result in plain English.
Create it in Hunter for me, then confirm the important fields before you finish.
Create it in Hunter for me, then confirm the important fields before you finish.
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 OpenClaw. 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 OpenClaw 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
OpenClaw installed the Hunter skill but can't call the tools
The ClawHub skill teaches OpenClaw about Hunter, but the calls run through the ClawLink plugin and your connected account. Make sure Hunter is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
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.
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 OpenClaw Hunter integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Hunter: link your Hunter account once in the browser and OpenClaw can call the Hunter API through 26 ready-made tools — no custom code or token handling.
How do I add Hunter to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Hunter skill from ClawHub, then you click Connect in the dashboard to authorize Hunter. OpenClaw calls the tools 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 OpenClaw?
About two minutes. Sign in, click Connect next to Hunter in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Hunter working from chat.
OpenClaw installed the Hunter skill but can't call the tools
The ClawHub skill teaches OpenClaw about Hunter, but the calls run through the ClawLink plugin and your connected account. Make sure Hunter is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
