ATS Jobs — open roles and hiring changes

io.github.VovikPPublished by GitHub account VovikPv0.1.2Updated Oct 24, 2026

Open jobs and hiring changes from Greenhouse, Lever, Ashby, Workable, Teamtailor, SmartRecruiters

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Tracks open roles and hiring changes across six applicant tracking systems, returning only what changed since the last run.

What you can do
Given a company domain, it detects which applicant tracking system the company uses and returns its open roles. Four tools are exposed: find_job_board, list_jobs, detect_changes and hiring_summary. On repeat runs it reports only deltas such as roles opened or closed, title or location changes, salary changes, and derived signals like hiring acceleration or a hiring freeze. Each record carries provenance including source URL, HTTP status, fetch time and a confidence value.
When to use it
Useful for monitoring hiring at many companies over time, for recruiting or market research, or for answering questions about what a specific company is currently hiring for. It is a fit when you want change detection rather than a one-off job listing lookup.
Requirements
Runs locally over stdio, typically started with npx ats-jobs-mcp, so Node.js is needed. No authentication, API keys or environment variables are declared. It keeps state in a local file under the user's home directory, overridable with the ATS_MCP_STATE variable, and needs network access to public ATS endpoints. A hosted paid variant also exists.
Before you install
It writes a local state file so that change detection works between runs. It reads only public job board endpoints and strips recruiter personal data at parse time, but the domains you query are sent to third-party ATS services. The hosted option is billed per jobs processed, while the self-hosted server is free.

Installation

In SourceWeft

  1. Open ATS Jobs — open roles and hiring changes 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

Greenhouse, Lever, Ashby, Workable, Teamtailor Jobs API

One API for six applicant tracking systems: Greenhouse, Lever, Ashby, Workable, Teamtailor and SmartRecruiters.

Give it a company website. It finds the job board itself, returns every open role, and on every run after that returns only what changed — roles opened, roles closed, titles moved, salaries changed — plus derived hiring signals.

json
{ "domains": ["stripe.com", "spotify.com", "pleo.io"] }

No board tokens. No ATS knowledge required. No browser.

Two ways to run it

Hosted on ApifySelf-hosted MCP server
Setupnonenpx ats-jobs-mcp
State between runsmanagedlocal file
Scheduling, retries, storageincludedyour own
Price$1 per 1,000 jobsfree
Linkapify.com/feedworks/ats-jobs-apithis repo, mcp/

The logic is the same code in both. Pick whichever fits.

What you get

EventMeaning
job_indexedBaseline: an open role captured on the first run
job_postedA new opening appeared
job_closedAn opening disappeared
job_changedTitle, location, department or employment type changed
salary_changedCompensation changed
hiring_acceleratingThis month's postings are 2× or more the recent average
first_role_in_functionFirst ever hire in sales, AI/ML, security, data — a new budget line opened
hiring_freezePostings dropped to zero after steady hiring

Every record carries provenance: source URL, HTTP status, fetch time, job count, truncation flag and a confidence value — so an agent can verify before it acts, instead of trusting a claim.

MCP server

bash
npx ats-jobs-mcp

Four tools, usable by any MCP client — Claude Desktop, Cursor, VS Code, your own agent:

ToolQuestion it answers
find_job_boardWhich ATS does this company use, and what is its board token?
list_jobsWhat roles are open right now?
detect_changesWhat changed since the last time I looked?
hiring_summaryWhat is this company hiring for — which functions, which locations?

Claude Desktop config:

json
{  "mcpServers": {    "ats-jobs": { "command": "npx", "args": ["-y", "ats-jobs-mcp"] }  }}

State lives in ~/.ats-jobs-mcp/state.json. Override with ATS_MCP_STATE.

Why it stays cheap to run continuously

Every source is polled with If-None-Match. When nothing changed, the ATS answers 304 with no body.

Measured on the hosted Actor at 512 MB:

PathCompute
Nothing changed (304)0.000344 CU per run
Baseline, 143 jobs0.001386 CU

That is why watching hundreds of companies every few hours costs cents rather than dollars — and why this project will never open a headless browser to read a job board.

What it deliberately does not do

  • No personal data. Recruiter names, emails and phone numbers are stripped at parse time and never stored.
  • No headless browser, no proxies. Only public ATS endpoints that answer with JSON.
  • No false layoffs. If a source response may be truncated by paging, job_closed events are suppressed — a paging artefact must never look like a company shutting down hiring.

Supported sources

greenhouse · lever · ashby · workable · teamtailor · smartrecruiters

Detection order: a link on the company careers page → the board token guessed from the domain → Workable short links resolved through their redirect.

Companies that cannot be resolved return a source_unresolved record explaining why, instead of failing silently.

Recruitee and Personio are not listed because they are not verified working. Personio currently answers 429 to non-browser clients; Recruitee endpoints did not resolve in testing. This project does not claim coverage it cannot deliver.

Repo layout

src/          Apify Actor: adapters, diff engine, derived signalsmcp/          MCP server — the same engine, self-hostedtools/        discovery utilities (domain → ATS).actor/       Apify manifests and schemas

MIT licensed. Contributions welcome, especially new ATS adapters — the interface is one url() and one parse() function per system, see src/adapters/index.js.

Source: README.md at commit 0534585

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts