Integration

GetEmail.io integration

GetEmail.io (a Dun & Bradstreet company) finds and verifies professional email addresses. Find a prospect's email from their full name and company domain or name, optionally with extra LinkedIn profile data, read a previous search again by its id, and check whether an address is good or bad. Each email request uses one credit of the GetEmail.io plan; a search that finds nothing is refunded a few minutes later. Authentication is the API key from the GetEmail.io dashboard, sent as the api_key query parameter.

Connect GetEmail.io How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in GetEmail.io.Built from the 3 GetEmail.io tools below, on the connection you add once.

What you can do with GetEmail.io

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Email, 2 operations

find_emailFind emailGETFinds a prospect's email from their full name and company domain or name (1 credit, refunded later when nothing is found). Returns personal data. If is_terminated is false, read it later with get_find_email_status and the id.
verify_emailVerify emailGETVerifies whether an email address is good or bad. The first request starts the check: if is_terminated is false, call verify_email again with the same email after a short wait to get the verdict in verif_email_status.

Email search, 1 operation

get_find_email_statusGet find email statusGETReads a previous find_email search by its id without running a new search, with the same fields as find_email. Use it to check whether a search that was not yet terminated has finished.

Use GetEmail.io from Claude Code, Cursor or Codex

Connect GetEmail.io in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its GetEmail.io operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect GetEmail.io

Create your workspace
Sign up free. Nothing to install.
Connect GetEmail.io once
Add your GetEmail.io connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.