Mcp Gtm Hiring Signal Scraper

com.mambabuiltPublished by mambabuilt.comv1.4.1Updated Nov 7, 2026

Detects GTM hiring activity from company career pages via Greenhouse, Lever, Ashby. Clay-ready.

Overview

AI-generated overview

Scans a company's job board for sales, marketing and revenue operations roles and returns a GTM hiring signal as flat JSON.

What you can do
  • Scan a company domain's career page for open go-to-market roles and get a role count plus a high, medium or low signal strength
  • Detect the applicant tracking system in use across Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Personio
  • Filter matched roles by keyword and optionally return per-role details such as title, department, location and URL
  • Scan several domains in one batch run, one row per company
  • Compare against a previous role count and run date to report hiring velocity since the last run
When to use it
Useful for sales, GTM or revenue teams that want to qualify accounts by how aggressively they are hiring for sales, marketing and RevOps roles, and for feeding that signal into Clay, a CRM or an agent workflow on a schedule.
Requirements
Runs locally as an npm package via npx, so Node.js 18 or newer is needed. Requires an Apify account and an APIFY_TOKEN environment variable; all scraping runs on Apify. Desktop client only.
Before you install
The APIFY_TOKEN is a paid-service credential and should be kept out of shared configs. Runs are billed per result and per actor start on Apify, so batch scans and repeated runs cost money; max_charge_usd caps a single run but omitting it relies on the Apify account limit. Company domains are sent to Apify and its actor. Companies on other ATS platforms return a null platform and zero roles without an error, which can look like a negative signal.

Installation

In SourceWeft

  1. Open Mcp Gtm Hiring Signal Scraper in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

GTM Hiring Signal Scraper MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Gtm Hiring Signal Scraper MCP server]

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

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:

json
{  "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.

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.

Output

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.

Example output

json
{  "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"}

Features

  • Cascading ATS detection: Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Personio
  • GTM role filtering with 3-tier signal strength (high, medium, low)
  • Flat JSON output designed for Clay column mapping
  • Optional role_filter and ats_slug inputs
  • Batch mode (domains) and velocity mode for scheduled runs

Pricing

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

EventPrice (USD)
result (apify-default-dataset-item)0.05
Actor Start (apify-actor-start)0.00005

Full actor documentation

This 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


Mamba Labs GTM Suite

This server is one of 103 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

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

Source: README.md at commit 02b5e51

Tools

1

scan_gtm_hiring_signals

Scan GTM Hiring Signals

Scan company career pages to detect GTM hiring activity: open sales, marketing, and revenue operations roles, a role count, and a high, medium, or low signal strength. Reads the Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Personio job boards; a company on any other board returns a null ats_platform and a zero count, not an error. Use it to qualify an account before outreach, or on a schedule in velocity mode to see whether a company is ramping its GTM team. Use mode batch with domains for a list in one call. Output is Clay-ready flat JSON, one row per company. Requires an APIFY_TOKEN and consumes Apify credits per call.

Parametersmodedomainrequireddomainsats_slugrole_filtermax_charge_usdprevious_run_dateinclude_role_detailsprevious_gtm_role_count

Version history

5
  1. v1.4.1LatestNov 5, 2026
  2. v1.4.0Oct 16, 2026
  3. v1.3.1Oct 6, 2026
  4. v1.3.0Oct 6, 2026
  5. v1.2.0Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts