Domain To Linkedin Url Resolver
LocalAbout Domain To Linkedin Url Resolver
Domain To Linkedin Url Resolver is an MCP server from Mamba Labs that resolves a company’s LinkedIn page from its domain or name. For sales operations, CRM, and agent workflows, it returns a confidence score and optional firmographics from public search results without requesting LinkedIn pages.
Key features
- 01Resolve LinkedIn pages by domain or name
- 02Return high, medium, or low confidence
- 03Optional employee, industry, and HQ data
- 04Include social media links
- 05Handle one or multiple domains per call
Use cases
- 01Fill LinkedIn URLs in CRM records
- 02Prepare batches of company rows for Clay
- 03Enrich sales leads with firmographics
- 04Assess the confidence of a resolution
MCP support
Exposes the `resolve_linkedin_url` tool to MCP clients. It starts and polls the Apify actor, then returns results as flat JSON rows.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolverAPIFY_TOKENSecretApify API token from https://console.apify.com/account/integrationsLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
1Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| company_domain | string | No | Bare company domain without https:// and without a trailing slash. Example: stripe.com. Required if company_name is not provided. |
| company_name | string | No | Company name. Required if company_domain is not provided. |
| includeFirmographics | enum | No | When "true", also fetches the public LinkedIn company page to add employee_count_approx, industry, hq_location, follower_count and company_description. Off by default because it is the most expensive step, a full residential-proxied page fetch. The firmographic fields are present but null when it is off. Sent as a string for Clay compatibility.false | true |
| skipCache | enum | No | When "false", the default, a successful resolution is cached for 7 days and reused, skipping the residential HEAD and the search work. Set "true" to force a fresh resolution. Sent as a string for Clay compatibility.false | true |
Details
From the project READMEDomain 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
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, nohttps://and no trailing slash. Example:stripe.comcompany_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 reademployee_count_approx,industry,hq_location,follower_count, andcompany_descriptionfrom 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
includeFirmographicsis true - One domain or a list per call
Pricing
Domain to LinkedIn URL Resolver is pay per event on Apify.
| Event | Price | Fires when |
|---|---|---|
apify-actor-start | $0.00005 | Once per run, on start, one event per GB of memory (minimum one). Apify's start event. |
apify-default-dataset-item | $0.006 (FREE tier), down to $0.0051 on GOLD and above | Once per row written to the dataset. |
max_charge_usd | number | Optional cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. |
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.
| Actor | Immutable Actor ID |
|---|---|
| GTM Hiring Signal Scraper | D7O1SA2EqwHGsGr1P |
| GTM Tech Stack Signal Enrichment | qyd7nNyqFPelQViBx |
| GTM Signals Aggregator | xKdRfnfFNkdMpFuNs |
| Job Board Keyword Signal Scanner | 4DvqpvhMR74NLcDDY |
| Domain to LinkedIn URL Resolver | 3HtnSaqPHOg1Qg5gx |
| ICP Fit Scorer | W161DT8W4kW55dMFh |
| Domain Deliverability Checker | 0tVgxI7A6o9jMlxmc |
| Company Firmographic Enricher | YlUtLWjfPpqykmB8g |
| Company Social Presence Mapper | 4k6CCemkgBDz18m2h |
| Company Identity Resolver | lr8fTRAmZCBZmuwwh |
| Company Change-Event Feed | oX44rS0fkEJ3rXLWe |
| Funding & Press Signal Scanner | FS13X6dhQVgX3XOM6 |
Built by Mamba Labs | npm | Apify Store
License
MIT
Built by Mamba Labs. https://apify.com/mambalabs
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.