Skip to Main Content

UnwrapEmail × Model Context Protocol

Email tools.Meet your AI.

Check an address. Clean up a list. Get the results. Bring UnwrapEmail into Codex, Claude Code, Cursor, and more AI clients to keep working in the conversation.

Your existing API token. Your account’s permissions. The same validation billing.

An example workflow
Find my latest bulk validation job. Check its progress and get the download link when it’s ready.
  1. Find the latest job

    list_bulk_validations
  2. Check progress

    get_bulk_validation
  3. Get the results

    get_bulk_validation_download

Your client calls the tools. UnwrapEmail returns your account’s data.

23 tools, one connection

From a quick check to a whole workflow.

MCP gives your AI client tools to work with UnwrapEmail directly. Ask for the result you need, then use it alongside your code or your next decision.

Explore all tools and permissions
  1. Check an email

    Validate and normalize an address. Ask for disposable, role-based, and no-reply signals. Enable domain checks when you need MX and registry data.

  2. Work through a whole list

    Submit up to 10,000 email strings or a CSV with up to 100,000 rows. Keep the job ID, check progress, and retrieve a temporary CDN download link when it’s ready.

  3. Put your contacts to work

    Find contacts, inspect enrichment data, update names or addresses, and request CSV exports. Full-access tokens also allow contact deletion.

  4. Manage your domain blacklist

    Read your custom blacklist or replace it with an updated domain list. Replacement affects the entire list, so keep the entries you still need.

  5. See how your account is doing

    Check your subscription and usage, or ask for daily analytics over a date range. Bring the numbers into your planning without leaving your client.

Make the connection

Bring your token. Pick your client.

Start in Settings → API Tokens. The Connect with MCP panel has the endpoint, client search, configuration, and supported commands.

MCP endpoint

https://api.unwrap.email/mcp Open API token settings
  1. Choose your access

    Use an active subscription and an API token. Read-only tokens can inspect data and validate single emails; full access also enables submissions and changes.

  2. Add the configuration

    Choose your client in the dashboard and follow its token setup instructions. Copy its configuration or supported installation command. Keep the token secret out of your project files.

  3. Ask your first question

    Reconnect your client, then ask for current usage or the progress of an existing job. It discovers only the tools your token can use.

Good to know.

Permissions, usage, and the way jobs run.

What does a read-only token allow?
Read-only tokens can view contacts, job progress, downloads, blacklists, account details, and analytics. They can also validate a single email, which records usage and may create or update a contact. Full-access tokens also allow bulk submissions, export creation, contact changes, and blacklist replacement.
How does billing work?
MCP uses your active UnwrapEmail subscription. Validation follows the same billing and accounting as the REST API, including single-email validation with read-only tokens. Discovering tools and ordinary lookups do not add validation usage.
How do CSV uploads and background jobs work?
Your client prepares a signed upload URL, uploads the CSV bytes with its HTTP or file tools, then submits the upload ID and email column. CSVs support up to 50 MiB and 100,000 rows. Bulk validation and contact exports return identifiers immediately; check progress in separate calls and request a download link when ready.
Can my client change my account or billing?
Account deletion, profile changes, token management, and billing actions stay in the dashboard. Full-access MCP tokens can permanently delete contacts and replace the entire custom domain blacklist. The connection uses an API token, not a browser login or an OAuth flow.