MCP Linkedin Company Presence Mapper

What mcp-linkedin-company-presence-mapper does

The mcp-linkedin-company-presence-mapper MCP server connects an MCP client to the Mamba Labs LinkedIn Company Page Mapper actor on Apify. Its main operation, map_linkedin_company_presence, accepts a company domain, an optional company name, or a LinkedIn company handle.

For a resolved public page, the server can return the exact follower count shown by LinkedIn. It can also read public firmographic fields: industry, declared company size band, headquarters, founded year, specialties, and website. The result includes a per-platform status so callers can distinguish a successful lookup from a missing page, an unavailable value, a blocked request, or an identity mismatch.

This is a read-only lookup tool. It does not provide employee lists, employee growth, post engagement, or other information unavailable from a logged-out LinkedIn page.

How it works

When given a domain, the actor performs discovery, checks the candidate against the supplied company name when available, fetches the public page, and parses the requested fields. A handle skips discovery and goes directly to the fetch. If a guessed LinkedIn slug resolves to another company, the result is reported as identity_mismatch rather than silently accepting the page.

Each MCP call starts an Apify actor run, waits for completion, and reads its dataset. The run can wait for up to 1,800 seconds at 512 MB. If it is still running when the wait ends, the response contains the run ID and an Apify console link instead of discarding the run.

Successful lookups are cached for seven days by default. Set skipCache to true when a fresh fetch is required. includeFollowerCounts defaults to true; disabling it resolves the profile URL without fetching follower counts. includeFirmographics defaults to true and controls extraction of the public company details.

Setup and configuration

The mcp-linkedin-company-presence-mapper MCP server requires Node.js 18 or newer and an Apify API token. Configure it as an npm-launched stdio server, passing the token through the APIFY_TOKEN environment variable:

{
  "mcpServers": {
    "mamba-linkedin-company-presence-mapper": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-linkedin-company-presence-mapper"],
      "env": { "APIFY_TOKEN": "your-apify-token" }
    }
  }
}

The token is obtained from the Apify account integrations page. Apify charges credits for actor starts and for applicable company checks, profile resolutions, and follower-count extractions. Current prices are maintained on the actor page and may vary by Apify plan.

Tools and capabilities

The mcp-linkedin-company-presence-mapper MCP server exposes one documented tool:

• map_linkedin_company_presence
  • company_domain: bare domain such as shopify.com.
  • company_name: optional name used to improve discovery and identity validation.
  • handle: optional LinkedIn company slug such as shopify.
  • includeFollowerCounts: request follower-count extraction; defaults to true.
  • skipCache: bypass the seven-day successful-result cache; defaults to false.
  • includeFirmographics: request public company details; defaults to true.

Status values include ok, not_found, not_extractable, blocked, identity_mismatch, and skipped. A null value means the lookup could not establish an answer, while false represents a confirmed negative where applicable.

Limitations and notes

The mcp-linkedin-company-presence-mapper MCP server depends on data visible from LinkedIn while logged out. LinkedIn can block a request, omit a field, or expose a profile without exposing the requested count. These cases are represented in the status output rather than treated as confirmed absence.

The service consumes Apify credits on calls. The actor starts with 512 MB, producing one actor-start event under the documented pricing model. Use includeFollowerCounts: false when only the profile URL is needed, and use a handle when discovery is unnecessary.