List Employees of a Company with MCP

This page is about setup and prompts. For the REST roster endpoint and the full field list, see Company Employees. Other clients are on the MCP hub, and the wider catalog is under enrichments.

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

You can also run /mcp inside a session and finish the browser sign-in there.

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.

The tool

There is no dedicated roster tool. The agent uses search_leads, which the server lists as leadocean_search_leads, with the domain filter. It costs 1 record per person returned.

The REST twin is GET /v1/companies/{domain}/people. It lists the whole roster with no filters. Over MCP you get the roster and the filters in one tool.

Prompts that work

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

A question about size goes to count_leads, which is free. A request for names goes to search_leads. Addresses and numbers need get_lead or find_phone, 1 record each.

What the agent gets back

The result is a data array of thin leadocean.person.v1 records plus a meta block. Field names are from the search docs and the OpenAPI spec, September 2026. Values below are placeholders.

{
  "data": [
    {
      "profile_data": {
        "profile_full_name": "Alex Example",
        "profile_headline": "Head of Sales at Acme",
        "profile_url": "https://www.linkedin.com/in/alex-example"
      },
      "contact_data": {
        "contact_current_experiences": [
          { "job_title": "Head of Sales", "company_domain": "acme.com" }
        ],
        "has_email": true,
        "has_phone": false,
        "email_status": "verified",
        "email_type": "work"
      },
      "meta": { "source_ids": { "person_id": "1234567890" } }
    }
  ],
  "meta": { "nextCursor": "(opaque string)" }
}

Search returns flags, never addresses. Read email_status before you ask for an address. About a fifth of people have no LinkedIn URL, so profile_url can be null. Use person_id for those.

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: ["stripe.com"] on 2026-10-01. It returned total: 10301, totalIsExact: true, credits: 0. That counts mailable people (verified, catch_all_valid or catch_all), not everyone we hold. A roster that size hits the 10,000-row paging cap, so narrow it by title, seniority or country.

Troubleshooting

FAQ