mambalabsdev/mcp-job-board-keyword-signal-scanner

An MCP server that scans a company's job board for the roles you care about. It wraps the Mamba Labs Job Board Keyword Signal Scanner actor on Apify and returns a Clay-ready flat JSON row to any MCP client.
What's Inside
- What it does
- Quick start
- Prerequisites
- Example prompts
- Inputs
- Output
- Example output
- Features
- Pricing
- How each call runs
- Full actor documentation
- Mamba Labs GTM Suite
- License
What it does
Give it a company domain and a set of role categories, and it scans Greenhouse, Lever, Ashby, Workday, and Rippling for matching open roles. Pick from GTM, Engineering, Finance, Operations, Executive, or pass your own custom keywords. You get back a flat row of matched role counts and titles per category, ready for Clay, a CRM, or an AI agent workflow. All of the scanning 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_job_board_keywords tool will be available.
Prerequisites
- Node.js 18 or newer
- An Apify account with an API token
Example prompts
- "Is stripe.com hiring engineers? Scan their job board for Engineering roles."
- "Check openai.com for GTM and Executive openings."
- "Scan figma.com for Finance and Operations roles."
- "Look for roles matching 'machine learning' and 'platform' at datadoghq.com using custom keywords."
Inputs
Every input the tool accepts, generated from the server's own tool list.
| Input | Type | Required | Description |
| --- | --- | --- | --- |
| company_domain | string | yes | Bare company domain without https:// and without a trailing slash. Example: stripe.com |
| role_categories | array of GTM, Engineering, Finance, Operations, Executive, Marketing, HR, CustomerSuccess, Data, Product, Legal, Design, Custom | yes | One or more role categories to scan for. Twelve categories plus Custom, which is used together with custom_keywords. Matching on the actor side is case insensitive and ignores separators, so customer_success and Customer Success both reach CustomerSuccess, and sales resolves to GTM. |
| custom_keywords | array of string | no | Keyword strings to match when Custom is included in role_categories. Required only if Custom is requested. |
| enable_fallback | boolean | no | If true, falls back to a pre-indexed job database when the live ATS cascade finds nothing. |
| previous_roles_detected | string | no | Comma-separated matched role titles from a previous run, used to compute newly added or removed roles. |
| previous_run_date | string | no | ISO date of the previous run, e.g. 2026-03-15. Used for tracking changes over time. |
| max_charge_usd | number | no | Optional spending cap for this call, in USD. The actor stops before any charge that would take the run past this amount and keeps every row already charged. |
Output
The tool returns the actor's flat JSON row for the scanned company, including matched role counts and titles per requested category, the ATS platform detected, and optional change tracking. See the Apify Store page for the full output schema.