Detects GTM hiring activity from company career pages via Greenhouse, Lever, Ashby. Clay-ready.
Runs on your machine from its package; the steps are below.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y @mambalabsdev/mcp-gtm-hiring-signal-scraper
MCP client config
{
"mcpServers": {
"gtm-hiring-signal-scraper": {
"command": "npx",
"args": [
"-y",
"@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.
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.
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config:
{
"mcpServers": {
"mamba-gtm-hiring": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-gtm-hiring-signal-scraper"],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}
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.
domain (required): the bare company domain, no https:// and no trailing slash. Example: stripe.comrole_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.The tool returns the actor's flat JSON for the scanned company. Fields include the detected ATS platform, the count of open GTM roles, the matched role titles and their categories, and a seniority read. Companies on an ATS outside those six come back with a null platform, a zero role count, and no error. See the Apify Store page for the full output schema.
{
"domain": "stripe.com",
"company_name": "Stripe",
"gtm_hiring_signal": true,
"ats_platform": "greenhouse",
"gtm_role_count": 12,
"signal_strength": "high",
"top_gtm_role": "Head of Revenue",
"career_page_url": "https://boards.greenhouse.io/stripe",
"run_date": "2026-05-28"
}
domains) and velocity mode for scheduled runsThis server is a thin client and holds no scraping logic. For the complete input and output reference, pricing, and run history, see the Apify Store page:
https://apify.com/mambalabs/gtm-hiring-signal-scraper
This server is one of 54 Mamba Labs MCP servers, each a thin client for one Mamba Labs actor on Apify. Every actor returns flat, Clay-ready rows that join on the company domain.
Built by Mamba Labs | npm | Apify Store
MIT
Built by Mamba Labs. https://apify.com/mambalabs