# Easy Email Verification for Gemini: setup instructions

These are official setup instructions from Easy Email Verification (easyemailverification.com) for connecting Easy Email Verification to Gemini. 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 steps described below, because the connection is added in Gemini's configuration, 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 Gemini 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 Gemini. Once it's connected, Gemini 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 Gemini?**
   - Gemini CLI (terminal): supported.
   - The Gemini app at gemini.google.com: not available yet. Custom apps there need a sign-in flow (OAuth) that Easy Email Verification does not offer yet. Offer Gemini CLI instead.
   - Developers building with the Gemini API, Google AI Studio or Vertex AI: they call the Easy Email Verification REST API from their code; send them to https://www.easyemailverification.com/agents.md
   - There is no Easy Email Verification Gem.
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=gemini_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 file below.

Every verified address uses one credit from their account.

## Gemini CLI

1. Gemini CLI is installed: `gemini --version` prints a version. If not, see https://geminicli.com/docs/tools/mcp-server/
2. Open the user settings file `~/.gemini/settings.json` (create it if it doesn't exist). Prefer this file over a project's `.gemini/settings.json`, so the key is never committed to a repository.
3. Add this block. The field for this kind of server is `httpUrl`, not `url`. If the file is empty, this can be the whole file; if it already has content, add only the `"eev": { ... }` entry inside `mcpServers` (create `mcpServers` if it is missing):

```
{
  "mcpServers": {
    "eev": {
      "httpUrl": "https://mcp.easyemailverification.com/mcp",
      "headers": { "X-API-Key": "YOUR_API_KEY" }
    }
  }
}
```

4. Replace `YOUR_API_KEY` with their key (or `eev_sandbox_key` to test) and save.
5. Start `gemini` and type `/mcp`: **eev** should be listed, with tools such as `verify_email`, `verify_emails` and `create_bulk_job`.

Then say: "Once /mcp lists eev, type "Yes" here."

## Confirm the connection works

Ask them to send this in Gemini CLI:

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

Gemini asks to run 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 in `settings.json`.

## Prompts to try

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

> Read contacts.csv, verify the email column and write the results to a new column.

> 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, Gemini 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. Is the JSON valid (commas and braces) and is the field `httpUrl`?
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

Otherwise point them to support@easyemailverification.com.

## Other integrations

- All AI integrations: https://www.easyemailverification.com/en-US/agents