Open jobs read from a company's own careers system: Greenhouse, Ashby, Lever.
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.
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.
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 companyTitle, 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 schemaThe 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.
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 / hour gives no salary. An hourly rate is a different
quantity and reporting it as annual would be a confident lie.600 000 kr gives no salary. kr is Swedish, Norwegian and Danish.0.5% - 1.75% - Offers Equity gives no salary. Equity is not pay.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.
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.
| 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.
The server runs remotely. Point any MCP client that speaks Streamable HTTP at the URL and there is nothing to download:
{
"mcpServers": {
"ats-jobs": {
"url": "https://ats-jobs-api.groundtruthtools.workers.dev/mcp"
}
}
}
Checked 2026-09-13: of the job board servers in the official MCP registry, this is the only one with a remote transport. Every other one, including the PyPI build of this one, has to be installed first.
The same thing answers plain HTTP, for agents that do not speak MCP:
GET /openapi.json for a tool-calling agentGET /llms.txt for a model reading the service in proseGET /v1/jobs?company=stripe&limit=5pip install ats-jobs-mcp
Then add to your MCP client configuration:
{
"mcpServers": {
"ats-jobs": {
"command": "ats-jobs-mcp"
}
}
}
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.
MIT. Job postings belong to the employers who published them.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx ats-jobs-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-groundtruthtools-ats-jobs-mcp": {
"command": "uvx",
"args": [
"ats-jobs-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceats-jobs-mcppypiATS Jobs works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.