Icypeas

What Icypeas MCP server does

Icypeas MCP server exposes Icypeas’s email-search service through the Model Context Protocol. Its main function is to search for a professional email address using a person’s first name, last name, and either a company domain or company name. The returned match is intended to include Icypeas’s own certainty label.

This package belongs in the Search & Data Extraction category for workflows that enrich contact records, research prospects, or identify a likely business address from basic professional details. It is an independent, unofficial integration and is not affiliated with Icypeas.

How it works

The server sends requests to Icypeas’s email-search endpoint at https://app.icypeas.com/api/email-search. Authentication uses an Icypeas API key supplied as the _apiKey tool argument. The request is sent with an Authorization: Bearer <key> header, so callers must enable API access and obtain a key from the API section of their Icypeas dashboard.

The published Icypeas API documentation describes email discovery as asynchronous: the initial request enqueues a search, and an optional webhook can notify the caller when processing finishes. The integration includes defensive parsing for a results array at the top level or within an item object, selecting the first result containing a non-empty email address. That response handling is best effort rather than fully verified against a live authenticated request.

Setup and configuration

You can connect to the hosted MCP endpoint at https://gateway.pipeworx.io/icypeas/mcp, or run the package locally over standard input and output with npx -y @pipeworx/mcp-icypeas. The local mode does not require a Pipeworx account and exposes only this pack’s tool. The hosted endpoint also lists shared Pipeworx gateway tools, including routing and discovery utilities.

A client configuration for the hosted endpoint uses its URL directly. A local configuration uses npx as the command and -y @pipeworx/mcp-icypeas as its arguments. In either mode, provide the Icypeas key when calling the tool; the package does not provide a platform key.

Tools and capabilities

The Icypeas MCP server provides one documented pack-specific tool:

• icypeas_find_email: searches for a work email using optional first and last names, a required company domain or name, and the required _apiKey.

The hosted Pipeworx connection may show additional shared meta-tools because it is served through the wider gateway. Those tools are not part of the standalone package’s tool list. The gateway also offers ask_pipeworx for natural-language routing, while the local server handles only the Icypeas tool.

Limitations and notes

The exact successful response shape has not been verified with a live Icypeas key. In particular, it is not confirmed whether the initial endpoint response contains the email directly or returns an identifier such as item._id that must be polled through another results endpoint. If valid-key calls consistently report found: false, check for this asynchronous polling requirement before treating the person as having no discoverable email.

Unauthenticated requests and requests using an invalid bearer key were observed to return HTTP 401 with a user-not-found error. The possible values for the certainty field have also not been verified. The integration should therefore be tested with a real Icypeas account before relying on its parsing or result status in production.