UnwrapEmail now supports the Model Context Protocol (MCP). Connect Codex, Claude Code, or Cursor to your account and work with email validation, bulk jobs, contacts, exports, and usage from the same conversation where you are building or debugging your application.

You can ask your client to check an address, investigate a validation result, or retrieve a completed CSV export. It calls UnwrapEmail’s tools and uses the returned data to answer. Your existing API token connects it to your account.

Email validation in your workflow

When you are investigating a signup issue or preparing an import, a validation result is often one step in a larger task. MCP makes that step available directly to your AI client.

For example, try:

Validate alex@example.com with domain checks enabled. Explain the disposable, role-based, and MX signals in the result.

The validate_email tool returns the same validation data as the REST API, including MX and registry checks by default. Single-email, JSON bulk, and CSV bulk validation default to validate_domain: true; set it to false for faster checks without domain lookups.

You can then discuss the result alongside your application’s code and decide how your signup or import policy should handle it. Validation provides signals for that decision; it does not guarantee delivery to an inbox.

From one address to a whole list

The MCP server includes 23 tools covering the main UnwrapEmail workflows:

  • Email validation: check one address or submit a JSON list of up to 10,000 email strings.
  • CSV validation: prepare an upload, submit a file with up to 100,000 rows, and retrieve its results.
  • Contacts and exports: inspect contacts, update names or email addresses, delete contacts, and request CSV exports.
  • Domain blacklists: read or replace your account’s custom domain blacklist.
  • Account and usage: inspect your subscription, current usage, and usage analytics.

Once connected, you can ask:

Check the progress of my latest bulk validation job. If it has completed, get the download link.

Or:

Show my validation usage for the last seven days, including the daily totals.

Bulk validation and contact exports run asynchronously. Submission returns a job identifier; your client checks progress in separate calls and retrieves a download link when the job is ready. Results are delivered through temporary public CDN links, so large files do not need to fill the conversation.

For CSVs, the client first prepares a signed upload URL, uploads the file bytes using its HTTP or file tools, and then submits the job with the upload ID and email column name. Files can be up to 50 MiB. CSV bytes travel through the upload URL, not through MCP.

Connect with your existing API token

The server endpoint is https://api.unwrap.email/mcp.

  1. Open Settings → API Tokens in your UnwrapEmail dashboard. You need an active subscription and a valid API token.
  2. In Connect with MCP, choose Codex, Claude Code, or Cursor and copy the configuration.
  3. Set UNWRAP_EMAIL_API_TOKEN in the environment used to launch your client, then add the configuration and reconnect.

The configuration references the environment variable, so you can keep your token secret out of project configuration files. The MCP setup guide has the exact configuration for each client, the full tool list, and troubleshooting steps.

Permissions and billing stay familiar

Use a read-only token for viewing contacts, job results, exports, account details, and analytics. A full-access token also enables bulk submissions, export creation, contact changes, and blacklist replacement. Your client discovers only the tools its token is allowed to use.

Single-email validation is available with either token type. It records usage and may create or update contacts, including when called with a read-only token. Validation follows the same billing and accounting as the REST API. Discovering tools and ordinary lookups do not add validation usage.

Contact deletion is permanent. Replacing a blacklist replaces the entire list, so read the current entries first if you want to keep them. Account deletion, profile changes, API-token management, and billing actions remain in the dashboard.

Start with a single address or a lookup of an existing job. Then use the connection guide to bring the rest of your email workflow into your client.