Icypeas MCP Server
Provides containerization support for easier deployment and isolated execution of the MCP server
Used for managing environment variables, particularly the Icypeas API key needed for authentication
Used for package management and running build/start commands for the MCP server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Icypeas MCP Server find John Doe's work email at Acme Corporation"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Icypeas MCP Server
This is a Model Context Protocol (MCP) server that integrates with the Icypeas API to provide work email finding capabilities.
Features
Find work emails using name and company information
Related MCP server: Hatch MCP Server
Setup
Local Setup
Clone this repository
Install dependencies:
npm installCreate a
.envfile based on.env.exampleand add your Icypeas API key:ICYPEAS_API_KEY=your_api_key_hereBuild the server:
npm run buildStart the server:
npm start
Docker Setup
Clone this repository
Create a
.envfile with your Icypeas API keyBuild and run using Docker Compose:
docker-compose up -d
MCP Configuration
To use this server with an MCP client, add the following configuration to your MCP settings file:
{
"mcpServers": {
"icypeas": {
"command": "node",
"args": ["path/to/icypeas/dist/index.js"],
"env": {
"ICYPEAS_API_KEY": "your_api_key_here"
},
"disabled": false,
"autoApprove": []
}
}
}Available Tools
icypeas_find_work_email: Find a work email using name and company information
License
ISC
Available Tools
1 toolicypeas_find_work_emailC
Find a work email using name and company information.
Inputs: domainOrCompany (required), firstname (required), lastname (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct as it is the only one available.
The single tool name follows a consistent snake_case pattern with a clear verb_noun structure (find_work_email). Since there is only one tool, naming consistency is inherently perfect.
One tool is too few for a server's apparent scope, as it suggests a very limited functionality that may not support typical agent workflows. This feels thin and incomplete for a general-purpose server.
The server's domain appears to be email or contact lookup, but with only one tool, there are significant gaps. For example, there are no tools for verifying emails, updating contact information, or handling other related operations, which will likely cause agent failures in broader tasks.
Related MCP Connectors
Icypeas MCP — wraps the Icypeas email-search API (icypeas.com)
Model Context Protocol server for Studex tools, notifications, and profile integrations
Model Context Protocol server for todo.vu task management and time tracking.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides a seamless email management interface through Claude, allowing users to search, read, and send emails directly through natural language conversations.4114MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol server for Hatch API integration that provides tools for finding and verifying contact information including emails, phone numbers, LinkedIn profiles, and company data.51-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that integrates with Prospeo API to find work emails and enrich LinkedIn profiles.1-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects to RocketReach API, enabling AI assistants to find professional/personal emails, phone numbers, and enrich company data.1-