# 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  
**Views:** 3  
**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.

## 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 MCP server does

The mambalabsdev/mcp-domain-to-linkedin-url-resolver MCP server accepts a company domain or company name and attempts to identify the corresponding LinkedIn company page. Its response includes the LinkedIn URL and slug, along with a confidence value and the method used for resolution.

The returned data is formatted as a flat JSON row. Depending on the actor response, that row can include the company domain, company name, approximate employee count, industry, headquarters location, social links, and run date. The structure is intended for use in Clay, CRM enrichment, or agent workflows that need company-level context.

## How it works

This package acts as a thin MCP client rather than implementing the resolution process itself. It sends the request to the Mamba Labs Domain to LinkedIn URL Resolver actor running on Apify, then makes the actor result available to the MCP client.

The underlying process uses Google search and LinkedIn URL pattern matching, according to the documented feature list. Results include high, medium, or low confidence labels, allowing a downstream workflow to decide whether additional verification is needed. The server does not expose a separate local database or independent resolution algorithm in the provided documentation.

Input supports two optional fields:

- `company_domain`: a bare domain such as `stripe.com`, without `https://` or a trailing slash.
- `company_name`: the company name to resolve.

At least one field is required. If both are supplied, the domain is used first.

## Setup and configuration

The mambalabsdev/mcp-domain-to-linkedin-url-resolver MCP server requires Node.js 18 or later and an Apify account with an API token. Set the token in the `APIFY_TOKEN` environment variable. The token is obtained through the Apify account integrations page.

A Claude Desktop MCP configuration can launch the package through `npx`:

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

After adding the configuration and restarting Claude Desktop, the `resolve_linkedin_url` tool becomes available. The token placeholder in the example must be replaced with a valid Apify token before use.

## Tools and capabilities

The documented MCP tool is `resolve_linkedin_url`. It supports resolving either a domain or a company name and returns the actor's flat JSON output. Notable fields and capabilities include:

- LinkedIn company URL and LinkedIn slug
- High, medium, or low confidence scoring
- Resolution method reporting
- Approximate employee count
- Industry and headquarters information
- Social links when present
- Flat output suitable for Clay, CRM, and agent workflows

## Limitations and notes

Resolution depends on the Apify-backed actor, so an Apify account and API token are required. This MCP package does not contain the resolution logic or a separate local data source. The complete actor input and output schema, pricing, and run history are referenced in the Apify Store documentation rather than defined in the provided README.

The domain input should be normalized to the bare domain format documented by the project. A company name can be used instead, but the README does not specify how ambiguous names are disambiguated beyond returning a confidence score. The project is released under the MIT license.

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