Hunter on TexAu
Drive Hunter from your code, your CRM, or directly from Claude and Cursor. Every action is exposed as REST and as an MCP tool — no glue code, no Zapier middleman.
Top actions
Most-used Hunter actions
Quick links into the 4-action catalog. Each action page has the full input/output schema and a try-it widget.
Enrich Company (Hunter.io)
hunter-enrich-companyEnriches company information from a domain using Hunter.io Companies API.
Find Email Using Name and Company Domain (Hunter.io)
hunter-find-emailFinds a professional email address using a person's full name and company domain via Hunter.io.
Find Mobile Number Using Email (Hunter.io)
hunter-find-number-by-emailFinds and enriches a person profile from an email address using Hunter.io People API.
Find Mobile Number by LinkedIn URL (Hunter.io)
hunter-find-number-by-linkedin-urlFinds and enriches a person profile from a LinkedIn URL using Hunter.io People API.
What teams build
Common Hunter workflows on TexAu
Enrich on the way in
Trigger on a new Hunter record, run the 32-integration waterfall, write verified fields back.
Sync to a TexAu Table
Pull on a schedule, enrich in a Table, push the deltas back. Custom field mapping, conflict resolution, observable trace.
Call from Claude
Every action above is also an MCP tool. Wire Hunter into Claude, Cursor, or any MCP client with one config block.
Related other apps
Other Other integrations
FAQ
Hunter on TexAu — common questions
How many Hunter actions does TexAu support?
TexAu supports 4 public Hunter actions. Every action is callable as REST and as an MCP tool.
Can I call Hunter from Claude or Cursor?
Yes. Every Hunter action on TexAu is exposed as an MCP tool, so Claude, Cursor, and any MCP client can invoke it directly.
Is Hunter sync bidirectional on TexAu?
TexAu can both pull from and push to Hunter via REST. For full bidirectional CRM-style sync, see the CRM apps in the directory.