Find Work Email with MCP

Ask Claude or Cursor for someone's work email and the agent calls get_lead with reveal_email. One URL, OAuth sign-in, 1 record per lookup.

This page is about setup and prompts. For the REST endpoint and field detail, see Find Work Email. Other clients are on the MCP hub.

Connect the server

The server is https://api.leadocean.io/mcp. It signs in with OAuth 2.1, so there is no key to paste. Create a free account first.

Claude Code. The command format is from the Claude Code MCP docs, September 2026:

claude mcp add --transport http leadocean https://api.leadocean.io/mcp
claude mcp login leadocean

The second line opens the browser sign-in. Running /mcp inside a session does the same.

Cursor. Add a remote server to mcp.json, in the url form shown in the Cursor MCP docs, September 2026:

{
  "mcpServers": {
    "leadocean": {
      "url": "https://api.leadocean.io/mcp"
    }
  }
}

Cursor starts the OAuth sign-in the first time the server is used. Other clients follow the same pattern, see the LeadOcean MCP docs. Windsurf users: find work emails in Windsurf.

The tool

There is no separate work email tool over MCP. The agent uses get_lead, which the server lists as leadocean_get_lead, with reveal_email set to true. It costs 1 record per call, and reveal_email adds nothing.

Send one identifier. There is no name plus company lookup: the agent searches by domain first, then enriches by person_id.

The call returns every contact point, so the agent picks the work address itself. It should keep an address only when its type is work and its status is verified or catch_all_valid. The REST twin, GET /v2/people/email/work, does that filtering for you.

Prompts that work

Put a record limit in the prompt. "Stop after 25 records" is enough for the agent to hold a batch.

The agent picks the tool from your wording. A question about size goes to count_leads, which is free. A request for an address on a named person goes to get_lead, which costs 1 record. Ask it to skip anyone whose result has no work address, and to say "none held" instead of guessing.

What the agent gets back

The result is one leadocean.person.v1 object. Contact points sit in contact_data, per the enrich docs, September 2026. Values below are placeholders.

{
  "success": true,
  "data": {
    "contact_data": {
      "has_email": true,
      "email_status": "verified",
      "contact_emails": [
        { "email": "jane.doe@example.com", "type": "work", "status": "verified", "verified_batch_date": "2026-09-14" }
      ],
      "contact_current_experiences": [
        { "company_name": "Example Inc", "company_domain": "example.com", "job_title": "Title" }
      ]
    }
  },
  "meta": { "credits": 1 }
}

Nothing is invented: a field we do not hold is null, and an empty contact_emails means we hold no address. Read type first. work is the current employer. work_other is a business address at a different company, usually one the person left, and the likeliest to bounce. verified_batch_date is the date of a verification run, shared by a whole batch.

Free checks first

count_leads, list_enum_values and get_account spend no records. Run them before any paid call.

On 2026-09-30 count_leads returned 5,066 mailable people for jobLevel VP, jobFunction Sales & Business Development, country CA. Mailable means verified, catch_all_valid or catch_all. A fresh run on 2026-10-01 returned a 503 (no_source), so that is the latest count we hold.

Troubleshooting

FAQ