# How to connect Hunter to OpenClaw > Connect Hunter to OpenClaw in one click. 8 Hunter tools your agent can call from chat. No API keys. Web version: https://claw-link.dev/openclaw/hunter ClawLink gives OpenClaw a more practical Hunter setup than rolling your own integration. 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. ## Hunter MCP for OpenClaw Looking for a Hunter MCP server for OpenClaw? ClawLink connects Hunter to OpenClaw and exposes 8 Hunter tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Hunter integration](https://claw-link.dev/hermes/hunter) works the same way. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/hunter ## Setup It takes three steps to connect OpenClaw to Hunter. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Hunter** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect hunter # connect Hunter (browser OAuth) npx -y @useclawlink/cli actions hunter # list available actions npx -y @useclawlink/cli run hunter --input '' # execute (add --confirm for writes) ``` ## What the OpenClaw Hunter integration can do 8 Hunter tools are ready for OpenClaw once the account is connected. ### All 8 Hunter tools for OpenClaw | Tool | What it does | |---|---| | **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 | | **Company enrichment** `hunter_company_enrichment` | Get enrichment information for a company | | **Combined enrichment** `hunter_combined_enrichment` | Find person and company info from an email | | **Discover companies** `hunter_discover_companies` | Search and retrieve companies matching criteria | | **Create lead** `hunter_create_lead` | Create a new lead | | **Create leads list** `hunter_create_leads_list` | Create a new leads list | ## Example prompts **Domain Search** > Search Hunter for what I need, summarize the results, and tell me the next best action. **Email Finder** > Use Hunter to email finder and walk me through the result in plain English. **Email Verifier** > Use Hunter to email verifier and walk me through the result in plain English. **Company Enrichment** > Use Hunter to company enrichment and walk me through the result in plain English. ## 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. | 8 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 8 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### 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. ### The Hunter account is connected but the action fails Check whether the connected account has access to the workspace, inbox, store, or project you are trying to use. Most failures at this stage are permission mismatches, 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. ### 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 8 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 or API keys. ### 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. ## Related - [Connect Apollo](https://claw-link.dev/openclaw/apollo) — Search leads and manage contacts - [Connect HighLevel](https://claw-link.dev/openclaw/highlevel) — All-in-one sales, marketing, and CRM platform - [Connect HubSpot](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines