io.github.groundtruthtools/ats-jobs-mcp
Enables querying open job postings directly from company applicant-tracking systems (Greenhouse, Ashby, Lever), finding a company's job board, listing and comparing roles, and accessing salary data, all without scraping or API keys.
README
ats-jobs-mcp
<!-- mcp-name: io.github.groundtruthtools/ats-jobs-mcp -->
An MCP server for open job postings, read first-hand from the applicant-tracking system behind a company's careers page. Ask your assistant what Anthropic is hiring for and get the answer from Anthropic's own board, not from a job aggregator's index.
Built on the job board APIs that Greenhouse, Ashby and Lever publish so third parties can build job sites. No scraping, no API key, no account, no personal data.
Why this exists
Those APIs are open, documented, and useless unless you already know the
company's board name: that Anthropic's is anthropic, Ramp's is ramp,
Mistral's is mistral.ai.
None of the vendors publishes a directory of its customers, and none could,
since no vendor knows about the others. Checked 2026-08-24: sitemap.xml on
job-boards.greenhouse.io, boards.greenhouse.io, jobs.lever.co and
apply.workable.com all 404 or redirect.
So this ships one: 7,479 company boards, every one confirmed against the vendor's own API, each carrying the date it was confirmed.
Three tools
find_company_board — which system is a company on?
Give it a company name. Get the system and the board name, plus how many roles were open when the board was last confirmed.
list_open_jobs — every open role at one company
Title, department, location, employment type, workplace type, posted date, a
parsed salary range where the employer publishes one, and a verify_url
pointing at the employer's own advert.
compare_companies — several companies, one schema
The thing no single vendor can do. Companies on Greenhouse and companies on Ashby come back with the same field names, so they can be compared directly. One company failing does not lose the others.
Salaries, parsed, and refused when unclear
Ashby prints pay as "$211.4K - $290.6K". Greenhouse prints it in cents,
sometimes as several bands at once. Neither is filterable, so both are turned
into numbers:
"salary_min": 211400.0, "salary_max": 290600.0,
"salary_currency": "USD", "salary_text": "$211.4K - $290.6K"
The parser refuses more often than it guesses, deliberately:
$50 - $80 / hourgives no salary. An hourly rate is a different quantity and reporting it as annual would be a confident lie.600 000 krgives no salary.kris Swedish, Norwegian and Danish.0.5% - 1.75% - Offers Equitygives no salary. Equity is not pay.- Bands in two currencies are never spanned into a range that exists nowhere.
salary_text always keeps what the employer actually wrote, so nothing is
lost when the parser declines.
Every parsed figure is tested against the employer's own structured
baseSalary block, the one published for Google to index — not against a
number someone typed into a test.
No personal data
Recruiter names are never returned. Email addresses and phone numbers are removed from job descriptions, because descriptions genuinely carry them and a column of work addresses is a marketing list rather than a job feed.
Unlisted Ashby postings are dropped, because Ashby's documentation says plainly that they should not be shown publicly.
Coverage, stated honestly
| System | Boards in the directory |
|---|---|
| Greenhouse | 4,168 |
| Ashby | 3,311 |
Lever is readable but has almost no boards in the directory yet, so name it
directly (lever:spotify) or pass its careers URL. Workable has a confirmed
endpoint but no adapter yet, so it is not listed at all: a directory entry for
something nothing can read is a broken promise.
Install
pip install ats-jobs-mcp
Then add to your MCP client configuration:
{
"mcpServers": {
"ats-jobs": {
"command": "ats-jobs-mcp"
}
}
}
Relation to the hosted version
The same parsing runs as an Apify Actor at apify.com/groundtruth/ats-job-listings, which adds scheduling and an incremental mode that returns only postings you have not been sent before. This server is free, runs on your machine, and takes no cut of anything.
tests/test_core_parity.py fails if the two copies of the parsing logic drift
apart.
Licence
MIT. Job postings belong to the employers who published them.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
E2B
Using MCP to run code via e2b.