io.github.groundtruthtools/ats-jobs-mcp
OfficialAllows searching and retrieving live open job postings from employer career pages hosted on Greenhouse, including title, department, location, employment and workplace type, posted date, parsed salary ranges, and a verification link to the employer's own job advert.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@io.github.groundtruthtools/ats-jobs-mcpCompare software engineer openings and salaries at Anthropic and OpenAI"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: recruiting-jobs-mcp
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-mcpThen 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.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to fetch and structure job postings from major ATS platforms (Greenhouse, Lever, Ashby, etc.) directly, eliminating copy-paste and context loss.352MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to pull live job listings from major ATS platforms (Greenhouse, Lever, Ashby, Workable), Hacker News hiring threads, and detect hiring signals on company career pages.
- AlicenseAqualityAmaintenanceSearch and read public Ashby job boards for named companies, with filtering, full job details, and side-by-side compensation comparison. No API key required.6562MIT
- FlicenseNot gradedqualityCmaintenanceEnables searching and retrieving startup job listings from Wellfound with salary, equity, and company signals like Y Combinator backing, funding stage, and remote status.
Related MCP Connectors
Semantic search over 3.5M+ live US job postings pulled straight from company ATSes. Read-only.
Live job postings from 30+ ATS feeds and job boards, one schema. Live results need a Bearer key.
Unified jobs search over official feeds + ATS boards (USAJOBS, Adzuna, Muse, Greenhouse, Lever...)
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/groundtruthtools/ats-jobs-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server