Mcp Domain To Linkedin Url Resolver
Turn a prospect’s domain or company name into a LinkedIn company URL plus firmographics while researching accounts in Claude or Cursor.
Overview
com.mambabuilt/mcp-domain-to-linkedin-url-resolver is a MCP server for the Idea phase that resolves a company domain or name to its LinkedIn URL with confidence scoring and firmographics.
What is this MCP server?
- Resolves company domain or legal name to LinkedIn company URL with a confidence score
- Returns firmographic fields alongside the URL for list building and CRM enrichment
- stdio npm MCP package @mambalabsdev/mcp-domain-to-linkedin-url-resolver v1.0.1
- Runs on Apify; requires APIFY_TOKEN from Apify console integrations
- Fits Clay-style and agent workflows that need LinkedIn anchors from bare domains
- Server version 1.0.1
- Single npm package with stdio transport
- One required secret: APIFY_TOKEN
Community signal: 1 GitHub stars.
What problem does it solve?
You have a list of domains or company names from a landing page scrape or spreadsheet but no reliable LinkedIn company URLs for research, outreach, or firmographic joins.
Who is it for?
Solo builders enriching prospect or competitor lists from domains during idea-stage research with an Apify account already set up.
Skip if: Teams that need person-level LinkedIn URLs, email finding, or CRM sync without any Apify token or external API budget.
What do I get? / Deliverables
Your agent returns LinkedIn URLs and firmographics you can paste into Clay, a CRM, or a validate-phase outreach experiment without manual LinkedIn search.
- LinkedIn company URL for a given domain or company name
- Confidence score and firmographic fields suitable for list enrichment
- Agent-callable structured output for downstream Clay or spreadsheet workflows
Recommended MCP Servers
Journey fit
Account and competitor research in the Idea phase often starts with a domain or name—this server is the canonical shelf for that enrichment step before outreach or validation. Research subphase covers mapping unknown companies to structured profiles (LinkedIn + firmographics) for ICP and competitor lists.
How it compares
MCP enrichment integration backed by Apify, not an agent skill or a full sales engagement platform.
Common Questions / FAQ
Who is com.mambabuilt/mcp-domain-to-linkedin-url-resolver for?
It is for solo and indie builders who use Claude Code, Cursor, or similar agents to research companies and want LinkedIn company URLs from domains or names without leaving the editor.
When should I use com.mambabuilt/mcp-domain-to-linkedin-url-resolver?
Use it in the Idea phase when you are building ICP lists, mapping competitors, or preparing Clay tables and need LinkedIn anchors from bare company identifiers.
How do I add com.mambabuilt/mcp-domain-to-linkedin-url-resolver to my agent?
Install the npm package @mambalabsdev/mcp-domain-to-linkedin-url-resolver, configure stdio transport in your MCP client, and set the required APIFY_TOKEN environment variable from Apify account integrations.