emailfinder-mcp
README.md
# emailfinder-mcp
MCP server for [emailfinder.dev](https://emailfinder.dev) — find verified professional email addresses directly from AI assistants like Claude, Cursor, and Kiro.
## Tools
| Tool | Description | Credits |
|------|-------------|---------|
| `find_email_by_person` | Name + domain → email | 1 |
| `find_email_by_linkedin` | LinkedIn URL → email | 1 |
| `find_company_emails` | Domain → list of emails | 5 |
| `find_decision_maker` | Role + domain → email | 5 |
| `validate_email` | Verify email deliverability | Free |
Credits are only charged when an email is found.
## Setup
Get your API key at [emailfinder.dev/dashboard/settings](https://emailfinder.dev/dashboard/settings).
### Claude Desktop / Cursor / Kiro
Add to your MCP config:
```json
{
"mcpServers": {
"emailfinder": {
"command": "npx",
"args": ["-y", "emailfinder-mcp"],
"env": {
"EMAILFINDER_API_KEY": "ef_live_your_key_here"
}
}
}
}
```
### Example usage
> "Find the email for the CEO of stripe.com"
> "Find emails at openai.com"
> "What's the email for https://www.linkedin.com/in/johnsmith?"
TDQS
A3.6/5.0
Scored across 5 tools
Disambiguation5/5
Each tool targets a distinct use case: name+domain, LinkedIn, company domain, decision maker role, and validation. No confusion between them.
Naming Consistency4/5
All tools use verb_object pattern, but four start with 'find_' while one starts with 'validate_'. This minor inconsistency is still clear and readable.
Tool Count5/5
5 tools cover the essential email finding operations without being excessive or insufficient for the server's purpose.
Completeness5/5
The toolkit covers all common email discovery needs: individual lookup, LinkedIn-based, company-wide, decision maker targeting, and validation. No obvious gaps.
Maintenance
ActivityInactive
ResponsivenessNo issues