LinkedIn URL to Email with MCP

Paste a LinkedIn profile URL into Claude or Cursor and the agent calls get_lead for you. One URL, OAuth sign-in, 1 record per match and nothing for a miss.

This page is about setup and prompts. For the REST endpoint and the field table, see LinkedIn to Email. Other clients are on the MCP hub. The opposite direction is email to LinkedIn with MCP, with the REST version at Email to LinkedIn.

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

Then run /mcp in a session and finish the browser sign-in. claude mcp login leadocean does the same from the shell.

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 are listed in the LeadOcean MCP docs.

The tool

The tool is get_lead. The server lists it as leadocean_get_lead. It costs 1 record per call, and 0 when it finds nobody.

Send one identifier. There is no tool named for work email, so the agent passes linkedin_url with reveal_email: true. The REST twin for a single checked work address is GET /v2/people/email/work. The MCP tool returns the full person record instead, at the same 1 record.

Prompts that work

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

Tell the agent to send only to verified or catch_all_valid addresses and to report the status of every row. LeadOcean gives no refund for bounced emails.

What the agent gets back

The result is one leadocean.person.v1 object plus a meta block. Field groups are from the enrich docs, September 2026. Values below are placeholders.

{
  "person": {
    "profile_data": {
      "profile_full_name": "Jane Doe",
      "profile_url": "https://www.linkedin.com/in/jane-doe"
    },
    "contact_data": {
      "has_email": true,
      "email_status": "verified",
      "contact_emails": [
        { "email": "jane.doe@acme.com", "type": "work", "status": "verified" }
      ]
    }
  },
  "meta": { "source": "...", "key_hash": "...", "schema": "leadocean.person.v1" }
}

Read type before sending: work is the person's current employer, work_other is usually one they have left. Unknown values are null. If contact_emails is empty, we hold no address for that person.

Free checks first

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

We ran count_leads with domain: ["hubspot.com"] on 2026-10-01. It returned total: 5931, totalIsExact: true, credits: 0. That counts mailable people at the domain (verified, catch_all_valid or catch_all), not everyone we hold. It tells the agent whether a company is worth a paid lookup.

Troubleshooting

FAQ