Mapping a domain to a LinkedIn company page is guesswork at the margins, and returning a confidence score next to the URL is the difference between an enrichment you can gate automatically and one somebody has to check. The cost model is the thing to settle before looping it: the call is read-only, but each one consumes Apify credits, so running it across a whole prospect list is a billing decision as much as a technical one.
A single-tool resolver: resolve_linkedin_url maps a company domain or company name to its LinkedIn company URL and returns the match as a flat, Clay-ready JSON row.
- resolve_linkedin_url returns the LinkedIn company URL together with a confidence score, so a weak match can be routed to review instead of written straight into a record.
- The same row carries firmographics — employee count, industry and headquarters — plus social links, which folds what would otherwise be a second enrichment lookup into the first call.
- Output is a flat JSON row shaped for Clay, and either company_domain or company_name is enough to start; the call is read-only.
An APIFY_TOKEN, since the resolution runs on Apify and consumes Apify credits per call. You must supply at least one of company_domain or company_name.
One command plus a key — npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver, then supply credentials