mcp-gtm-hiring-signal-scraper
by mambalabsdev
README.md
# GTM Hiring Signal Scraper MCP Server
[](https://smithery.ai/servers/mambabuilt/mcp-gtm-hiring-signal-scraper) [](https://glama.ai/mcp/servers/mambalabsdev/mcp-gtm-hiring-signal-scraper) [](https://registry.modelcontextprotocol.io/v0/servers?search=com.mambabuilt/mcp-gtm-hiring-signal-scraper&limit=1) [](https://www.npmjs.com/package/@mambalabsdev/mcp-gtm-hiring-signal-scraper) [](https://www.npmjs.com/package/@mambalabsdev/mcp-gtm-hiring-signal-scraper) [](https://github.com/mambalabsdev/mcp-gtm-hiring-signal-scraper/blob/main/LICENSE) [](https://mcpservers.org/servers/mambalabsdev/mcp-gtm-hiring-signal-scraper)
<a href="https://mcprush.com/to/gtm-hiring-signal-scraper-mcp?ref=badge"><img width="380" height="200" src="https://mcprush.com/badge/gtm-hiring-signal-scraper-mcp/card.svg" alt="Gtm Hiring Signal Scraper MCP server" /></a>
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](#what-it-does)
- [Quick start](#quick-start)
- [Prerequisites](#prerequisites)
- [Example prompts](#example-prompts)
- [Inputs](#inputs)
- [Output](#output)
- [Example output](#example-output)
- [Features](#features)
- [Full actor documentation](#full-actor-documentation)
- [Mamba Labs GTM Suite](#mamba-labs-gtm-suite)
- [License](#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:
```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.
| Event | Price (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 58 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.
- Browse every server: https://mambabuilt.com/servers
- Browse every actor on the Apify Store: https://apify.com/mambalabs
> Built by [Mamba Labs](https://mambabuilt.com) | [npm](https://www.npmjs.com/org/mambalabsdev) | [Apify Store](https://apify.com/mambalabs)
## License
MIT
Built by Mamba Labs. https://apify.com/mambalabs
TDQS
A4.5/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of tool misselection or overlapping purposes. The single tool has a clearly defined scope and internal modes that do not create cross-tool ambiguity.
Naming Consistency5/5
The tool name 'scan_gtm_hiring_signals' follows a clear snake_case verb_noun pattern. With only one tool, consistency is inherently perfect.
Tool Count3/5
A single tool is borderline thin for the server's purpose. While it covers the core scanning operation, the rubric treats 1-2 tools as marginal, and there is no separate tool for configuration, result retrieval, or board management.
Completeness4/5
The tool covers scanning across multiple ATS platforms, batch mode, velocity mode, and outputs structured JSON. For the narrow purpose of detecting GTM hiring signals, the surface is largely complete, with only minor potential gaps like separate board listing or historical trend queries.
Maintenance
ActivityActive
ResponsivenessResponsive