io.github.groundtruthtools/ats-jobs-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_company_boardA | Find which applicant-tracking system a company's careers page runs on. Greenhouse, Ashby, Lever and Workable all publish open job board APIs, and all of them are unusable unless you already know the company's board name. None of them publishes a directory of its customers, and none could, since no vendor knows about the others. Use this first when you have a company name rather than a careers URL. |
| list_open_jobsA | Every open job at one company, read from its own careers system. Returns 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. Salaries are refused rather than guessed: an hourly rate, an ambiguous currency, or bands in two currencies all yield no figure, and salary_text keeps whatever the employer actually wrote. |
| compare_companiesA | Open jobs across several companies at once, in one schema. This is the thing no single applicant-tracking system can do: each vendor only knows about its own customers. Companies on different systems come back with the same field names, so they can be compared directly. One company failing does not lose the others; each failure is reported beside the results that did work. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: one discovers the ATS board, one lists jobs for a single company, and one compares jobs across companies. There is no meaningful overlap or ambiguity between them.
All tool names follow the same verb_noun snake_case pattern: compare_companies, find_company_board, and list_open_jobs. The naming is consistent and predictable.
Three tools is well-scoped for this server's purpose. Each tool occupies a necessary step in the workflow, and none feel redundant or missing.
The tool set covers the full intended workflow: discover the ATS system, list open jobs at a company, and compare jobs across companies. There are no obvious dead ends or missing operations for this read-only domain.