# mambalabsdev/mcp-domain-to-linkedin-url-resolver [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/mambalabsdev/mcp-domain-to-linkedin-url-resolver  
**GitHub Stars:** 2  
**npm Downloads (last month):** 1027  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mambalabsdev-mcp-domain-to-linkedin-url-resolver

## Description
Resolves a company domain or name to its LinkedIn company URL with confidence scoring and firmographic metadata.

## Tools
Capabilities this server exposes over MCP:

- **resolve_linkedin_url** — Resolve a company domain or name to its LinkedIn company URL. Returns the LinkedIn URL with a confidence score, plus firmographics such as employee count, industry, and headquarters, and social links, as a flat, Clay-ready JSON row. Provide at least one of company_domain or company_name. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-domain-to-linkedin-url-resolver": {
    "command": "npx",
    "args": ["-y","@mambalabsdev/mcp-domain-to-linkedin-url-resolver"],
    "env": {
      "APIFY_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `APIFY_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What mambalabsdev/mcp-domain-to-linkedin-url-resolver does

mambalabsdev/mcp-domain-to-linkedin-url-resolver turns a company domain or name into a LinkedIn company URL. Results include the matched company identity, LinkedIn slug, resolution method, and a confidence value of `high`, `medium`, or `low`. Each row can also include Facebook, Instagram, X, and YouTube URLs.

The response is flattened for downstream enrichment workflows. Optional firmographic fields include approximate employee count, industry, headquarters, follower count, and company description. These fields are populated from search-result snippets only when firmographic enrichment is enabled.

## How it works

The package starts the Mamba Labs Domain to LinkedIn URL Resolver actor on Apify and waits for the run to finish. Resolution uses public search results and checks slug variants implied by the supplied company identity. The resolver does not request pages from LinkedIn itself.

Supply at least one of `company_domain`, `company_name`, or `domains`. If both a domain and name are supplied, the domain takes precedence. The `domains` option accepts multiple bare domains and produces one output row per domain. A seven-day cache is used by default; `skipCache` forces a new resolution.

## Setup and configuration

The runtime requires Node.js 18 or newer, an Apify account, and an Apify API token. Set the token as `APIFY_TOKEN` in the MCP client's environment. For Claude Desktop, the package can be launched with `npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver`.

Relevant inputs include:

- `company_domain`: a bare domain such as `stripe.com`, without a protocol or trailing slash.
- `company_name`: the company name to resolve.
- `domains`: an array of bare domains for multi-domain runs.
- `batchSize`: number of domains processed together, from 1 to 10; the default is 2.
- `includeFirmographics`: enables firmographic fields; the default is false.
- `skipCache`: bypasses the seven-day cache; the default is false.

## Tools and capabilities

The server exposes `resolve_linkedin_url`. It returns fields such as `linkedin_company_url`, `linkedin_slug`, `confidence`, `resolution_method`, social URLs, firmographic values, `run_date`, and degradation status fields. The operation is read-only.

A single call can resolve one company or a list of domains. The flat output can be passed to Clay, a CRM, or another agent workflow without reshaping nested records.

## Limitations and notes

Every resolution runs through Apify and consumes Apify usage. Charges include actor-start and dataset-item events; the underlying actor also supports an optional USD maximum charge for a run. Firmographic values are null when enrichment is disabled or when search snippets do not contain the requested data.

A failed Apify run is returned as an error with its run ID and status. The server is a thin client, so the resolution logic and actor-level behavior are handled by the Apify actor rather than locally.

_Full upstream README: https://allmcps.com/mcp/mambalabsdev-mcp-domain-to-linkedin-url-resolver/readme_