# ATS Jobs Aggregator MCP (`aicatraz/ats-jobs-aggregator-mcp`) Actor

Multi-source ATS job records from Greenhouse, Lever, and Ashby public boards. Search and filter by company, title, location, source, and remote. Standby MCP. Independent aicatraz dataset.

- **URL**: https://apify.com/aicatraz/ats-jobs-aggregator-mcp.md
- **Developed by:** [AI Catraz](https://apify.com/aicatraz) (community)
- **Categories:** AI, MCP servers, Lead generation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 mcp tool calls

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## ATS Jobs Aggregator MCP

Multi-source job records from public Greenhouse, Lever, Ashby company boards, and public hiring.cafe job pages.

Each row is one open role. Filter by company, title, location, source, or remote. Cross-source duplicates are merged into one record with a `sources` list.

### Fields

| Field | Meaning |
|---|---|
| `record_id` | Stable id (`gh_*`, `lv_*`, `ab_*`, or `hc_*`) |
| `source` | Primary source: `greenhouse`, `lever`, `ashby`, or `hiring_cafe` |
| `sources` | All sources that contributed to this record |
| `primary_source` | Same as preferred `source` after dedupe |
| `company` / `company_slug` | Employer name and board slug |
| `title` | Job title |
| `location` | Location string when listed |
| `department` | Department or team when listed |
| `employment_type` | Full-time / contract / etc. when listed |
| `is_remote` | Whether the posting looks remote |
| `job_url` | Public posting URL for this role |
| `posted_at` / `updated_at` | Timestamps when the source provides them |
| `description_snippet` | Short plain-text snippet when available |
| `record_status` | `active` or `stale` |

### Tools

MCP: `https://aicatraz--ats-jobs-aggregator-mcp.apify.actor/mcp`

| Tool | Output |
|---|---|
| `job_stats` | Counts by source and company, including multi-source merges |
| `list_sources` | Sources with job and company counts |
| `list_jobs` | Paginated jobs (filter by source, company, location, remote) |
| `get_job` | One record by `record_id` |
| `search_jobs` | Search title, company, location, department |
| `export_jobs` | JSON or JSONL export |

See the Apify Store pricing panel for current event charges.

### Example

```json
{
  "record_id": "gh_stripe_8172487",
  "source": "greenhouse",
  "sources": ["greenhouse", "hiring_cafe"],
  "company": "Stripe",
  "company_slug": "stripe",
  "title": "Abuse Investigator",
  "location": "Dublin",
  "is_remote": false,
  "job_url": "https://stripe.com/jobs/search?gh_jid=8172487",
  "record_status": "active"
}
```

### Updates

Standby serves the current store over MCP. Input `mode=refresh` rebuilds job records from curated public boards and public hiring.cafe job pages, then dedupes across sources.

### Notes

- Independent aicatraz dataset, not affiliated with Greenhouse, Lever, Ashby, hiring.cafe, or the listed employers
- Job URLs point at individual public postings
- When the same role appears on an ATS board and hiring.cafe, one merged record is kept and `sources` lists both

# Actor input Schema

## `mode` (type: `string`):

standby = serve MCP HTTP at /mcp (default). refresh = rebuild job records from public Greenhouse, Lever, and Ashby company boards plus public hiring.cafe job pages, dedupe across sources, write records, push stats to dataset, then exit.

## Actor input object example

```json
{
  "mode": "standby"
}
```

# Actor output Schema

## `mcpServer` (type: `string`):

Streamable HTTP MCP endpoint while the Actor run is live in Standby.

## `jobs` (type: `string`):

Job rows produced by mode=refresh (and available to MCP tools in Standby).

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("aicatraz/ats-jobs-aggregator-mcp").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("aicatraz/ats-jobs-aggregator-mcp").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call aicatraz/ats-jobs-aggregator-mcp --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,aicatraz/ats-jobs-aggregator-mcp"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/0YJTCTQJpQnGe82jT/builds/aruVtxsQlxhobo8yP/openapi.json