SkillTide Submit
Official description7 sourcesMCP servers8d ago
mambalabsdev/mcp-domain-to-linkedin-url-resolver

mambalabsdev/mcp-domain-to-linkedin-url-resolver

MCP server for Domain to LinkedIn URL Resolver. Resolves a company domain or name to its LinkedIn company URL with confidence scoring and firmographics via Apify. Clay-ready output.
View on GitHub ↗Direct link · no redirect page
Config template (adjust for your client)
claude mcp add mcp-domain-to-linkedin-url-resolver -- npx -y mcp-domain-to-linkedin-url-resolver
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
2 ★ · mambalabsdev/mcp-domain-to-linkedin-url-resolver · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 2 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository mambalabsdev/mcp-domain-to-linkedin-url-resolver;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals

Domain to LinkedIn URL Resolver MCP Server

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

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:
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.
Source
awesome · https://github.com/mambalabsdev/mcp-domain-to-linkedin-url-resolver
Browse by field
MCP servers
Traction
2 ★
added
yesterday

More in MCP servers

All 5,525 in MCP servers →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index