Can I use Hunter as a CLI?

Yes. KosmoKrator exposes a Hunter CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Hunter through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Hunter tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Hunter credentials stored?

Hunter credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Hunter MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Hunter MCP, CLI, and Lua Integration for AI Agents

Hunter integration docs for AI agents: MCP gateway setup, Hunter CLI commands, Lua API reference, credentials, and function schemas.

Hunter for agents

Credentials can be configured manually in web or CLI hosts.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Agent Surfaces

Hunter CLIHeadless setup, JSON output, direct function calls. Hunter MCPExpose selected tools to local MCP clients. Hunter LuaAgent-facing namespace and Lua reference. FeedbackReport missing tools, auth issues, or bad metadata.

Machine-Readable Metadata

integration_slug: hunter
route_slug: hunter
package: hunter
auth_strategy: api_key
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true

Function Catalog

Function	Type	Parameters	Description
`hunter.hunter_domain_search`	Read `read`	4	Search for professional email addresses associated with a domain. Returns email addresses found for the company, along with contact names, positions, and social profiles. Supports filtering by email type (personal or generic).
`hunter.hunter_email_finder`	Read `read`	3	Find the most likely professional email address for a person based on their name and company domain. Returns the email with a confidence score and sources where the email was found.
`hunter.hunter_email_verifier`	Read `read`	1	Verify the deliverability of an email address. Checks whether the email is valid, the mailbox exists, and accepts mail. Returns a result status (deliverable, undeliverable, risky, or unknown) along with confidence scores and SMTP details.
`hunter.hunter_email_count`	Read `read`	1	Get the total number of email addresses Hunter.io has found for a domain. Returns counts broken down by email type (personal, generic) and department. This endpoint does not consume API credits.
`hunter.hunter_list_leads`	Read `read`	2	List leads stored in your Hunter.io account. Supports pagination with limit and offset parameters. Returns lead details including email, name, and associated lists.
`hunter.hunter_get_lead`	Read `read`	1	Retrieve detailed information about a single lead by its ID. Returns the lead's email address, name, company, and any associated lists or custom fields.
`hunter.hunter_create_lead`	Write `write`	4	Create a new lead in Hunter.io. Requires an email address. Optionally include first name, last name, and a list ID to add the lead to a specific lead list. Returns the created lead object with its ID.
`hunter.hunter_get_current_user`	Read `read`	0	Get information about the authenticated Hunter.io account, including the user's name, email, plan details, and API usage (requests made and remaining). Useful for verifying the API key works and checking usage limits.