MCP Company Firmographic Enricher

What mambalabsdev/mcp-company-firmographic-enricher MCP server does

The mambalabsdev/mcp-company-firmographic-enricher MCP server exposes one read-only MCP tool, enrich_company_firmographics. Given a company domain, it collects publicly exposed firmographic information from the company website and returns a flat JSON record suitable for downstream enrichment workflows.

Returned fields can include:

• Employee band
• Industry
• Headquarters location
• Founded year
• Revenue estimate
• Company logo
• Company description
• source_signals, identifying the available source evidence
• data_completeness, indicating how complete the result is

The package is designed for agents that need to turn one or more domains into normalized company context without changing the source website or an external database.

How it works

The MCP client sends a tool call containing either a single bare domain through domain or multiple bare domains through domains. When both are provided, the list in domains takes precedence. An optional company_name can supply a fallback label when the target page does not expose a company name.

The underlying work runs through the Mamba Labs Company Firmographic Enricher actor on Apify. The server acts as a thin client: it routes the request to that actor and returns the actor’s result to the MCP client. Extraction is based on schema.org Organization JSON-LD and HTML meta tags found on the company site.

Batch requests support concurrent processing through batchSize, which defaults to 5 and cannot exceed 10. The skipCache option forces a new enrichment rather than using the seven-day result cache.

Setup and configuration

The mambalabsdev/mcp-company-firmographic-enricher MCP server requires Node.js 18 or newer and an Apify account with an API token. Configure the package as an MCP stdio server, passing the token as APIFY_TOKEN:

{
  "mcpServers": {
    "company-firmographic-enricher": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-company-firmographic-enricher"],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

The documented client setup uses Claude Desktop. After adding the configuration and restarting the client, the enrichment tool becomes available. Apify usage consumes credits per call, so the account and token must be able to run the backing actor.

Tools and capabilities

enrich_company_firmographics accepts these inputs:

• domain: one bare company domain, such as stripe.com.
• domains: an array of bare domains for batch enrichment.
• company_name: an optional fallback company label.
• batchSize: concurrent domains per batch wave, with a default of 5 and a maximum of 10.
• skipCache: a boolean that bypasses the seven-day cache when set to true.

The tool is read-only. It returns structured firmographics rather than performing updates, writes, or mutations. The output’s provenance signals and completeness score help an agent distinguish available source evidence from missing fields.

Limitations and notes

The mambalabsdev/mcp-company-firmographic-enricher MCP server depends on the target company exposing useful information in its JSON-LD or HTML metadata. The provided material does not guarantee that every field will be present, and the completeness score should be checked for each result.

Every call uses the Apify-backed actor and consumes Apify credits. A valid APIFY_TOKEN and compatible Apify account are therefore required. The package does not describe additional data sources, write operations, or enrichment beyond the firmographic fields returned by its single tool.

The project is licensed under MIT. Its README links to the Apify actor documentation for the complete actor-level input, output, pricing, and run-history reference.