KosmoKrator

sales

Hunter MCP Integration for CrewAI

Connect Hunter to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

8 functions 7 read 1 write API key auth

Connect Hunter to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Hunter MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-hunter": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=hunter",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=hunter --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Hunter instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Hunter Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Hunter integration catalog.

MCP toolSource functionTypeDescription
integration__hunter__hunter_domain_search hunter.hunter_domain_search Read 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).
integration__hunter__hunter_email_finder hunter.hunter_email_finder Read 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.
integration__hunter__hunter_email_verifier hunter.hunter_email_verifier Read 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.
integration__hunter__hunter_email_count hunter.hunter_email_count Read 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.
integration__hunter__hunter_list_leads hunter.hunter_list_leads Read List leads stored in your Hunter.io account. Supports pagination with limit and offset parameters. Returns lead details including email, name, and associated lists.
integration__hunter__hunter_get_lead hunter.hunter_get_lead Read 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.
integration__hunter__hunter_create_lead hunter.hunter_create_lead Write 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.
integration__hunter__hunter_get_current_user hunter.hunter_get_current_user Read 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.

Related Hunter Pages