MCP Server

Enrich a company domain into firmographics via Apify: employees, industry, HQ, revenue, logo, age.

Local serverstdioGo

What is the MCP MCP server?

Most developer tooling work still happens through a UI a human drives. MCP MCP server moves it into the conversation instead. Enrich a company domain into firmographics via Apify: employees, industry, HQ, revenue, logo, age.

The short version

An MCP server that exposes the Mamba Labs Company Firmographic Enricher as a single tool. Install one package and give your MCP client a way to turn a company domain into structured firmographics, wrapping the Mamba Labs actor on Apify and returning Clay-ready flat JSON with source provenance.

The tools it exposes

The server publishes 2 tools. What each one is for:

  • enrich_company_firmographics — enrich a company domain into employee band, industry, HQ, founded year, revenue estimate, logo, and description, parsed from the company's
  • Actor — Immutable Actor ID

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: APIFY_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js 18 or newer - An Apify account with an API token

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — enrich_company_firmographics, Actor — is a fair guide to whether it matches your workflow. It is maintained by com.mambabuilt; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
enrich_company_firmographicsenrich a company domain into employee band, industry, HQ, founded year, revenue estimate, logo, and description, parsed from the company's schema.org/Organization JSON-LD and HTML meta tags. Every record includes a sourc
ActorImmutable Actor ID

How to install the MCP MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js 18 or newer - An Apify account with an API token
VariableDescriptionRequired
APIFY_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP to enrich company firmographics.
  • Use MCP to Actor.

Frequently asked questions

It connects MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (enrich_company_firmographics, Actor) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP directly.