Bring Email Finder
to Cursor
Learn how to connect Hunter to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Hunter MCP Server?
Connect your Hunter account to any AI agent and power your email prospecting through natural conversation.
What you can do
- Domain Search — Find all professional email addresses associated with a domain or company name
- Email Finder — Discover the most likely email address for a specific person by name and company
- Email Verification — Check the validity and deliverability of any email address with confidence scores
- Email Count — Check how many email addresses are available for a domain before searching
- Contact Enrichment — Retrieve all available professional data (title, company, social profiles) for an email address
- Lead Management — Create, list, update, and delete leads in your Hunter CRM with lead list organization
- Account Monitoring — Track remaining API credits and account usage
How it works
1. Subscribe to this server
2. Enter your Hunter API Key from the account dashboard
3. Start finding emails from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Sales Teams — find decision-maker emails, verify addresses before outreach, and save leads to your CRM
- Recruiters — discover candidate contact information by name and company
- Marketing Teams — build verified email lists, enrich contact databases, and manage prospecting pipelines
Built-in capabilities (12)
Save lead to CRM
Get contact intel
Find personal email
Check credits
Check email availability
Get lead info
List lead lists
List lead profiles
Delete lead record
Find emails for domain
Modify lead data
Check deliverability
Why Cursor?
Cursor's Agent mode turns Hunter into an in-editor superpower. Ask Cursor to generate code using live data from Hunter and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Hunter in Cursor
Hunter and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Hunter to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Hunter in Cursor
The Hunter MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Hunter for Cursor
Every tool call from Cursor to the Hunter MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I find all professional email addresses for a specific company?
Yes. Use search_domain_emails with a domain (e.g., 'stripe.com') or company name (e.g., 'Stripe') to retrieve all professional emails found for that organization. Each result includes the email, confidence score, position, and source URLs. Use get_domain_email_count to preview how many emails are available before using search credits.
Can I verify if an email address is valid before sending outreach?
Yes. The verify_email_address tool checks the validity and deliverability of any email address. It returns a status (deliverable, undeliverable, risky, unknown), confidence score, and details about the email server (MX records, SMTP check, accept-all detection). This prevents bounces and protects your sender reputation.
How does Hunter API authentication work?
Hunter uses an API Key passed as a query parameter (?api_key=YOUR_KEY) in all requests to api.hunter.io/v2. This differs from the typical Bearer token pattern. Your API key is available in the Hunter dashboard under Account > API. Free accounts include 25 searches and 50 verifications per month.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.