ATS Jobs Feed MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. Required to make tool calls. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_company_ats_jobsA | List every open job for a list of companies, read from their own applicant tracking system boards: Greenhouse, Lever, Ashby, Workday, Workable, SmartRecruiters, Personio, Recruitee, Rippling, Oracle Recruiting, SuccessFactors, Teamtailor, BambooHR, ADP, UKG, Paylocity, and Breezy. Give companies as domains (stripe.com) or board URLs (https://jobs.lever.co/palantir). The board is found from the company site or by name, and a board that names another employer is rejected. Returns one row per job (title, department, location, remote flag, posting date, link, company domain) plus one free company row per company with the board found and job counts, or why no board was read. Optional filters on title, location, department, remote, and posting age; optional descriptions; only_new with a state_key returns only jobs not seen on the last run. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per job row returned and once per run start; company rows are free. |
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 1 tool
There is only one tool, so there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its purpose is clearly stated as listing open jobs from company ATS boards.
The single tool name follows a clear snake_case verb_noun pattern: list_company_ats_jobs. With only one tool there are no naming inconsistencies to compare against.
A single tool is thin for a server that also performs board discovery, validation, filtering, and incremental state tracking. Those responsibilities are packed into one broad operation rather than separated into focused tools.
For a read-only job feed, the tool covers the core listing workflow across many ATS providers with filters, descriptions, and only_new state. Minor gaps remain, such as fetching a single job by URL or separately listing supported providers/boards.