B2b Prospect Engine

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

MCP server for the Mamba Labs Prospect Engine actor on Apify.

Four modes in one actor: enrich companies you already have, discover who is hiring for your keywords, find contacts at a company, or run the whole chain end to end with an ICP gate in the middle.

Install

npx -y @mambalabsdev/mcp-b2b-prospect-engine

Claude Desktop

{
  "mcpServers": {
    "mamba-b2b-prospect-engine": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-b2b-prospect-engine"],
      "env": { "APIFY_TOKEN": "your-apify-token" }
    }
  }
}

Get an Apify token at console.apify.com/account/integrations.

Tool

run_prospect_engine

Four modes in one actor: enrich companies you already have, discover who is hiring for your keywords, find contacts at a company, or run the whole chain end to end with an ICP gate in the middle.

Billing

You are charged per company enriched, per contact verified and per job posting discovered, at different rates for basic and full enrichment. Vendor API calls are billed to you by those vendors directly. Set max_spend_usd to cap that vendor spend per run, and target_roles to skip paid lookups for contacts outside the roles you want. verify_position and personalize run on your own Anthropic key (claude_api_key) and are skipped without it.

Price per event on the Apify FREE plan, from the live pricing record; paid Apify plans pay less per event.

Pricing is on the actor's Apify page. Running this server consumes Apify credits.

What this server does and does not do

It is a thin client for the Apify actor. It passes your input through and returns the actor's output unchanged. Every behavior described above lives in the actor, not here.

Errors are surfaced, never swallowed. An invalid input, an invalid token, an exhausted balance, a timeout, or a run that returns anything other than a dataset all come back as an explicit tool error rather than as an empty result.

The tool starts the actor run and polls it to a finished status, so a long run is not cut off at 300 seconds. The run is allowed 1,800 seconds. If it is still going two minutes after that, the call stops waiting and returns the run ID with a link to it in the Apify Console, where the results land when it finishes. A run that does not succeed comes back as an error with its run ID and status. A full or find_contacts run over many companies can take several minutes, which is why this matters here.

Source

The actor is on the Apify Store. This wrapper is MIT licensed.

Built by Mamba Labs