Email to LinkedIn with MCP

Paste an email 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 Email to LinkedIn. Other clients are on the MCP hub. The opposite direction is covered in LinkedIn to email with MCP.

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 match.

Send one identifier. The tool description says to pass a work email. The REST twin is GET /v2/people/reverse, which returns a thin identity block. 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.

Keep reveal_email off. You already hold the address, and the profile URL comes back either way. The flag only adds every email and phone on file, and it costs no extra record.

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_headline": "Finance Manager at Acme",
      "profile_url": "https://www.linkedin.com/in/jane-doe"
    },
    "contact_data": {
      "has_email": true,
      "email_status": "verified",
      "contact_current_experiences": [
        { "company_name": "Acme", "company_domain": "acme.com", "job_title": "Finance Manager" }
      ]
    }
  },
  "meta": { "source": "...", "key_hash": "...", "schema": "leadocean.person.v1" }
}

Unknown values are null. About one person in five has no LinkedIn URL, so profile_url can be empty on a real match. Career history in resume_data comes back empty from the current source, so do not ask the agent for it.

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: ["apple.com"] on 2026-10-01. It returned total: 75304, 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 domain is worth a paid lookup.

Troubleshooting

FAQ