// claude + superagnt_

Can Claude find email addresses?

Only published ones on its own: Claude has no contact database, so web search finds an address only if someone posted it on a public page. Connect the superagnt_ MCP server and Claude finds a person's work email from their name and company, with a deliverability check.

It works the same in Claude Code, ChatGPT and Codex. In the run below, Claude found a founder's work address from a name and a domain in 10.3 seconds, and the check said valid.

Copy the setup prompt.
Your agent does the rest.

works with any agent+ 8 more

Connect the superagnt MCP server at https://mcp.superagnt.com/mcp/email-finder to this agent for me (I'll sign in through my browser). The setup guide for each kind of agent is at https://www.superagnt.com/install?facet=email-finder

or follow the detailed setup instructions

» a new workspace starts with the email finder tools already on. On an existing workspace, your agent switches them on during setup.

01// on its own, and with superagnt_

What Claude does alone, and what changes once it's connected

job	Claude on its own	with superagnt_
Find a work email	Web search, which finds an address only where someone published it.	`data_agnt_contacts` with `find_email`: a first and last name (or a full name) plus a company domain or name, and back comes the address and its status.
Check an address	No tool to test whether an address accepts mail.	`verify_email` checks the deliverability of any address you already have.
Addresses at a company	Whatever a search turns up.	`domain_emails` lists the addresses found for a domain, with first and last name, position and type, filterable by seniority and department.
A whole list	One search at a time.	`data_agnt_people` enriches people records in bulk: work email, role and company.

02// a real run

The job, run on superagnt_

Real tool calls on superagnt_'s staging environment, the same calls Claude makes once the server is connected. Each result is what the client received, trimmed where it says so and otherwise unchanged, and each wall time was measured around the call.

the ask

“Find Patrick Collison's work email at Stripe and check that it's deliverable.”

01Find the work email10.3 s wall timeOct 26, 2026, 12:40 UTC
→ calldata_agnt_contacts
```
{
  "action": "find_email",
  "first_name": "Patrick",
  "last_name": "Collison",
  "domain": "stripe.com"
}
```
← result
```
email: •••@stripe.com
status: valid
full_name: Patrick Collison
```
» Trimmed: the call's credit line. The part before the @ is masked on this page, at a fixed width; the tool returned the full address.
02Check it again on its own1.9 s wall timeOct 26, 2026, 13:01 UTC
→ calldata_agnt_contacts
```
{
  "action": "verify_email",
  "email": "•••@stripe.com"
}
```
← result
```
email: •••@stripe.com
status: valid
```
» Trimmed: the call's credit line. The address is masked on this page, at a fixed width; the call was made with, and returned, the full address.

The finder works down a waterfall of sources until one has the address, so a lookup takes longer than a check: 10.3 seconds here, against 1.9 seconds to check an address you already have. Billing is per result, and max_cost_cents caps what one lookup may spend.

03// set it up

Set it up in your client

Claude

01Open the prefilled Add custom connector dialog on claude.ai. One connector covers Claude on the web, Claude Desktop and Cowork.
02Click Add, then approve on the superagnt_ consent screen. It creates your superagnt_ account if you don't have one.
03Ask: “Find the work email for <name> at <company domain> and check it's deliverable.”

Free plans can add one custom connector. On Team and Enterprise plans, an owner adds it under Organization settings, Connectors (Anthropic).

Claude Code

01In a terminal, run claude mcp add --scope user --transport http superagnt https://mcp.superagnt.com/mcp/email-finder, then claude mcp login superagnt. The login opens a browser to approve; no API key needed.
02Start a new session.
03Ask: “Find the work email for <name> at <company domain> and check it's deliverable.”

ChatGPT

01In ChatGPT on the web, go to Plugins, select the plus button, then Add custom MCP server.
02Name it superagnt, enter the server URL under Connection, and set Authentication to OAuth. The server URL is https://mcp.superagnt.com/mcp/email-finder.
03Tick "I understand and want to continue", then select Create as a plugin. Sign in to superagnt_ when asked. No token needed.
04Install the plugin, then start a new chat, type @ and select superagnt.
05Ask: “Find the work email for <name> at <company domain> and check it's deliverable.”

ChatGPT takes custom MCP servers on the web, not on mobile. Business and Enterprise/Edu workspaces get every tool; Pro accounts get read and fetch actions, which is all this job needs (OpenAI).

Codex

01In a terminal, run codex mcp add superagnt --url https://mcp.superagnt.com/mcp/email-finder, then codex mcp login superagnt. The login opens a browser to approve.
02Start a new Codex session.
03Ask: “Find the work email for <name> at <company domain> and check it's deliverable.”

04// before you send

Finding an address is the start, not permission to email it

Check before you send: a status other than valid is a reason to skip the address, not to guess a variation.
Keep what you find in one place. Claude can write each result to a table in your superagnt_ database and check it before paying for the same lookup twice. See Can Claude save data between chats?
Cold email has rules where you and your recipients live. Follow them, and honor unsubscribes.