Domain to LinkedIn URL Resolver MCP Server

An MCP server that resolves a company domain or name to its LinkedIn company URL. It wraps the Mamba Labs Domain to LinkedIn URL Resolver actor on Apify and returns a Clay-ready flat JSON row to any MCP client.

What's Inside

• What it does

• Quick start

• Prerequisites

• Example prompts

• Inputs

• Output

• Example output

• Features

• Pricing

• Full actor documentation

• Mamba Labs GTM Suite

• License

Related MCP server: Company Identity Resolver MCP Server

What it does

Give it a company domain or a company name and it finds the matching LinkedIn company URL in public search results (it never requests a page on LinkedIn), with a confidence of high, medium, or low so you know how much to trust it, plus the company's Facebook, Instagram, X, and YouTube links, all in one flat row. Firmographics (employee count, industry, headquarters, follower count, description) are read from search result snippets when you set includeFirmographics to true; they are off by default and null when off or when no snippet states them. Pass domains to resolve a list in one call ready for Clay, a CRM, or an AI agent workflow. All of the resolution runs on Apify. This package is a thin client that calls the actor and hands back the result.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config:

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

Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The resolve_linkedin_url tool will be available.

Prerequisites

• Node.js 18 or newer

• An Apify account with an API token

Example prompts

• "Find the LinkedIn page for stripe.com."

• "What is the LinkedIn company URL for openai.com? Include the confidence score."

• "Resolve the company named Figma to its LinkedIn URL and firmographics."

• "Get the LinkedIn URL, employee count, and industry for datadoghq.com, with firmographics on."

• "Resolve the LinkedIn pages for stripe.com, notion.so, and figma.com."

Inputs

• company_domain (optional): the bare company domain, no https:// and no trailing slash. Example: stripe.com

• company_name (optional): the company name.

• domains (optional, array): a list of bare domains resolved in one run, one row per domain.

• batchSize (optional, integer): how many domains from the list are resolved at once. 1 to 10. Default 2.

• includeFirmographics (optional, boolean): also read employee_count_approx, industry, hq_location, follower_count, and company_description from search result snippets. No request is sent to LinkedIn. Default false. Those fields are null when it is off or when no snippet states them. The string forms "true" and "false" are accepted too.

• skipCache (optional, boolean): ignore the 7 day cache and resolve again. Default false. The string forms are accepted too.

Provide at least one of company_domain, company_name, or domains. If a domain and a name are both given, the domain takes priority.

Output

The tool returns the actor's flat JSON row per company: company_domain, company_name, linkedin_company_url, linkedin_slug, resolution_method, confidence (high, medium, or low), facebook_url, instagram_url, twitter_url, youtube_url, the firmographic fields employee_count_approx, industry, hq_location, follower_count, and company_description (null unless includeFirmographics is true), slug_mismatch, run_date, degraded, and degradation_reason.

Example output

Run with includeFirmographics set to true.

{
  "company_domain": "linear.app",
  "company_name": "Linear",
  "linkedin_company_url": "https://www.linkedin.com/company/linear-app",
  "linkedin_slug": "linear-app",
  "resolution_method": "google_search",
  "confidence": "high",
  "industry": "Software Development",
  "employee_count_approx": "201",
  "hq_location": "San Francisco, California, United States",
  "run_date": "2026-05-28"
}

Features

• Public search results (Brave, then Bing) checked against the slug variants the domain implies. No request is sent to linkedin.com

• Fixes the LinkedIn URL gaps in Clay native enrichment

• Confidence scoring (high, medium, low) and resolution_method

• Social links on every row; firmographics (employee count, industry, HQ) when includeFirmographics is true

• One domain or a list per call

Pricing

Domain to LinkedIn URL Resolver is pay per event on Apify.

The tool starts the actor run and polls it to a finished status, so a long run is not cut off at 300 seconds. A run that does not succeed comes back as an error with its run ID and status.

Full actor documentation

This server is a thin client and holds no resolution logic. For the complete input and output reference, pricing, and run history, see the Apify Store page:

https://apify.com/mambalabs/domain-to-linkedin-url-resolver

Mamba Labs GTM Suite

This server is part of the Mamba Labs GTM Suite, a fleet of twelve specialized MCP servers for go-to-market signal intelligence, each backed by a dedicated Apify actor.

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs