LinkedIn Company URL to Domain with MCP

Paste a LinkedIn company URL into Claude or Cursor and the agent calls get_company 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 lookup itself and the field list, see LinkedIn Company to Domain. The REST version is on the API page. 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. The same step is available as /mcp inside a session.

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 sign-in the first time the server is used. VS Code, Codex, Windsurf and Gemini CLI use the same URL, see the LeadOcean MCP docs.

The tool

The tool is get_company. The server lists it as leadocean_get_company. It costs 1 record per call.

Send one of the two. The domain you want is in the result at company_data.company_domain. The REST twin is POST /v1/companies/enrich, and it is the same lookup.

Prompts that work

Put the record limit in the prompt. The agent holds a batch to it.

The agent picks the tool from your wording. A question about reach goes to count_leads, which is free. A request for the domain of a named page goes to get_company.

What the agent gets back

The result is one leadocean.company.v1 object. The shape below follows the company docs, September 2026, trimmed. Every value is a placeholder (Acme), not a lookup we ran. The company_social_links field is how you check the match.

{
  "company_data": {
    "company_name": "Acme",
    "company_domain": "acme.com",
    "company_employees": { "number_of_employees": 1200, "number_of_employees_code": "1001-5000" },
    "company_primary_address": { "city": "Example City", "country_code": "US" },
    "company_social_links": {
      "linkedin": { "url": "https://www.linkedin.com/company/acme" }
    }
  },
  "company_metrics": { "completion_score": 94, "marketability_score": 81 },
  "meta": { "sources": ["own"], "schema": "leadocean.company.v1" }
}

Unknown values are null, never guessed. Ask the agent to compare company_social_links.linkedin.url with the URL you sent before it trusts the domain.

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 companyLinkedin: ["https://www.linkedin.com/company/stripe"] on 2026-10-01. It returned total: 10299, totalIsExact: true, credits: 0. That is mailable people at that company (verified, catch_all_valid or catch_all), not everyone we hold.

Troubleshooting

FAQ