enrich_company_firmographicsLABSCO SUMMARY
A domain in, a traceable company profile out.
One call fills the firmographic fields a GTM list needs, and each field arrives with the signal it came from rather than as an unattributed guess.
What it is
An MCP wrapper around Mamba Labs' firmographic enricher on Apify. One tool takes a company domain and returns flat, Clay-ready JSON parsed from the company's own schema.org/Organization JSON-LD and HTML meta tags.
What you get
- enrich_company_firmographics turns a domain into employee band, industry, HQ, founded year, revenue estimate, logo and description
- Every record carries a source_signals array, so each field traces back to where it was read
- A data_completeness score says how much of the profile actually came back
- Output is flat JSON, shaped to drop straight into Clay
- A batchSize input takes a list of domains rather than one at a time
Requirements
Node and the npm package. All of the work runs on Apify — this package is a thin client that routes the tool call there, so an Apify account carries the run.
Setup effort
One command plus a key — npx -y @mambalabsdev/mcp-company-firmographic-enricher, then supply credentials
USE CASES
01
Filling in a company row from nothing but a domain
Industry, size, headquarters and founding year come back in one call, in the flat shape a spreadsheet or Clay table expects.
02
Enriching a whole prospect list
A batch of domains goes through in one pass instead of one lookup at a time.
03
Deciding whether a profile is worth trusting
The completeness score and the source signals say how much of the record was actually found, so a thin profile is visible as thin.
04
Sizing an account before you route it
Employee band and revenue estimate are enough to decide whether a lead goes to self-serve or to a human, without opening a data vendor.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- npx on PATH
- Node.js 18 or later
- APIFY_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @mambalabsdev/mcp-company-firmographic-enricherMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"company-firmographic-enricher": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-company-firmographic-enricher"
],
"env": {
"APIFY_TOKEN": "<YOUR_APIFY_TOKEN>"
}
}
}
}
