mambalabsdev/mcp-gtm-hiring-signal-scraper

An MCP server that detects go-to-market hiring activity from company career pages. It wraps the Mamba Labs GTM Hiring Signal Scraper on Apify and returns Clay-ready flat JSON to any MCP client.
What's Inside
- What it does
- Quick start
- Prerequisites
- Example prompts
- Inputs
- Output
- Example output
- Features
- Full actor documentation
- Mamba Labs GTM Suite
- License
What it does
Give it a company domain and it scans that company's job board for sales, marketing, and revenue operations roles across Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Personio. You get back a structured read on how hard that company is hiring for go-to-market, ready to drop into Clay, a CRM, or an AI agent workflow. All of the scraping runs on Apify. This package is a thin client that calls the actor and hands back the result.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config:
Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The scan_gtm_hiring_signals tool will be available.
Prerequisites
- Node.js 18 or newer
- An Apify account with an API token
Example prompts
- "Check if stripe.com is hiring for go-to-market roles right now."
- "Scan openai.com for sales and revenue operations job postings."
- "Is datadoghq.com ramping up GTM hiring? Use the GTM hiring scanner."
- "Pull the GTM hiring signal for figma.com and list which roles are open."
- "Scan stripe.com, figma.com, and notion.so for GTM hiring in one batch."
Inputs
- domain (required): the bare company domain, no https:// and no trailing slash. Example: stripe.com
- role_filter (optional): a list of GTM role keywords to filter on. Leave it out to use the built-in keyword list.
- ats_slug (optional): override the ATS board slug when it differs from the domain. Example: clay.com uses claylabs on Ashby.
- domains (optional): a list of bare domains scanned in one run when mode is batch, one row per company. domain is still required by the schema, so pass the first domain there too.
- mode (optional): single (default) scores domain; batch scores every entry in domains; velocity compares this run against previous_gtm_role_count and previous_run_date to report role changes since the last run.
- include_role_details (optional): when true, adds the full per role array (title, department, location, URL). Default false.
- previous_gtm_role_count (optional): the GTM role count from your previous run for this domain. Used in velocity mode to compute the delta, which is what makes a scheduled run cheap.
- previous_run_date (optional): ISO date of your previous run for this domain, for example 2026-07-15. Used in velocity mode to report the days between runs.
- max_charge_usd (optional): a cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. Omit it to rely on the maximum cost per run set in Apify.