# Easy Email Verification for Claude: setup instructions

These are official setup instructions from Easy Email Verification (easyemailverification.com) for connecting Easy Email Verification to Claude. They're written for you, the assistant, to act on. The person you're talking to pasted them so you can walk them through the setup inside this conversation. The only things they'll do themselves are the commands and clicks described below, because the connection is added in Claude's settings or terminal, not in chat.

Go one step at a time and wait for the person to confirm before moving on. Keep the language plain and skip the jargon. Stick to what's written here. If they ask about something this document doesn't cover, say you're not sure and point them to support@easyemailverification.com rather than guessing.

Reply in the language the person writes in. Keep every URL, command and configuration value exactly as written here.

Don't summarize this document back to them. Greet them briefly, explain MCP in one breath (below), ask which Claude they use, and go straight into that path.

## Explaining MCP in plain English

MCP (Model Context Protocol) is the standard plug that lets a tool like Easy Email Verification connect to an AI assistant like Claude. Once it's connected, Claude can verify email addresses for them from a normal conversation. Easy Email Verification's MCP server is `https://mcp.easyemailverification.com/mcp`; it is in beta.

## Step 1: check they're ready

1. **Which Claude?**
   - Claude Code (terminal or IDE extension): supported.
   - Claude Desktop (app): supported through a small connector program, `mcp-remote`; needs Node.js installed.
   - Claude.ai in the browser: not available yet. It needs a sign-in flow (OAuth) that Easy Email Verification does not offer yet. Offer Claude Code or Claude Desktop instead.
2. **An API key.** They can test first with the public sandbox key `eev_sandbox_key`, which needs no account and uses no credits but only accepts test addresses at `sandbox.easyemailverification.com`. For real addresses they need their own key:
   - create a free account at https://dashboard.easyemailverification.com/register?utm_source=claude_md
   - create a key at https://dashboard.easyemailverification.com/apisettings
   - treat the key like a password: never paste it into this chat or share it publicly. They put it only in the command or file below.

Every verified address uses one credit from their account.

Once they pick a client, follow only that section, then go to "Confirm the connection works".

## Claude Code

Have them run this in a terminal, replacing `YOUR_API_KEY` with their key (or with `eev_sandbox_key` to test):

```
claude mcp add --transport http --scope user eev https://mcp.easyemailverification.com/mcp --header "X-API-Key: YOUR_API_KEY"
```

`--scope user` makes it available in all their projects. Then they start a new Claude Code session (`claude`) and type `/mcp`: **eev** should show as connected, with tools such as `verify_email`, `verify_emails` and `create_bulk_job`.

Then say: "Once /mcp shows eev as connected, type "Yes" here."

## Claude Desktop

1. Check Node.js is installed: in a terminal, `node --version` should print v18 or later. If not, they install it from https://nodejs.org.
2. In Claude Desktop open **Settings → Developer → Edit Config**. This opens `claude_desktop_config.json`.
3. Add this block. If the file is empty, this can be the whole file; if it already has an `mcpServers` section, add only the `"eev": { ... }` entry inside it:

```
{
  "mcpServers": {
    "eev": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.easyemailverification.com/mcp", "--header", "X-API-Key:${EEV_API_KEY}"],
      "env": { "EEV_API_KEY": "YOUR_API_KEY" }
    }
  }
}
```

4. Replace `YOUR_API_KEY` with their key (or `eev_sandbox_key`), save, and quit and reopen Claude Desktop completely.

Then say: "Once Claude Desktop has restarted, type "Yes" here."

## Confirm the connection works

Ask them to send this in a **new** Claude conversation:

- with the sandbox key: `Verify valid@sandbox.easyemailverification.com and invalid@sandbox.easyemailverification.com`
- with their own key: `Verify [an address they know]`

Claude asks permission to use the Easy Email Verification tool (each call can use credits), then shows **valid**, **invalid** or **unknown** with the reason. **unknown** means the server gave no reliable answer; it is neither valid nor invalid.

If they tested with the sandbox key, remind them to replace it with their own key the same way (in Claude Code: `claude mcp remove eev --scope user`, then the add command again).

## Prompts to try

> Check these addresses and tell me which ones to remove before my campaign: [up to 50 addresses]

> Verify [address] and suggest a fix if it has a typo.

> Read the CSV in this folder, verify the email column and add a column with the result.

> Verify all the addresses in leads.csv with a bulk job. Tell me how many credits it will use before starting, then summarize the results.

For lists of up to 10,000 addresses, Claude starts a bulk job and reads back a summary (totals and at most 50 example rows); the full results file is in the dashboard. Larger files can be uploaded there directly: https://dashboard.easyemailverification.com

## If something isn't working

1. Did they start a new session or conversation after adding it?
2. A message that the API key is invalid: check the key in https://dashboard.easyemailverification.com/apisettings (widget keys don't work; it must be an API key).
3. "No EEV credits left": plans at https://www.easyemailverification.com/en-US/pricing
4. Claude Desktop does not show the tool: check Node.js and that the JSON is valid (commas and braces).

Otherwise point them to support@easyemailverification.com.

## Other integrations

- All AI integrations: https://www.easyemailverification.com/en-US/agents
- For developers writing code against the API: https://www.easyemailverification.com/agents.md