ats-jobs-mcp
Related Servers
Alternatives to ats-jobs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to locate companies' public job boards across Greenhouse, Lever, Ashby and Workable, browse and filter live openings by keyword, location, department and remote status, and read full job descriptions with pay ranges and apply links. Requires no accounts, API keys or authentication, and is read-only.MIT
- AlicenseAqualityCmaintenanceEnables 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.3181 PyPI1MIT
- 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.-
- AlicenseNot gradedqualityCmaintenanceEnables searching live job postings pulled directly from 10 applicant-tracking-system APIs — including Greenhouse, Lever, Ashby, Workday, Personio, Recruitee, Teamtailor, Workable, SmartRecruiters and Breezy HR — using just a company website, domain or ATS handle, with filters for keywords, location, remote work and posting date. Also supports multi-company lookups, ATS detection, and stateless "only new since last call" monitoring for scheduled agents.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve live open roles from company career pages across Greenhouse, Lever, Ashby, Workday and other job boards, and to search open tech jobs by title, location, remote status, seniority, salary and date.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search live job listings across Greenhouse, Lever, Workday, Ashby, SmartRecruiters, Workable, Cornerstone, and Deel from a single remote endpoint, with filters for titles, location, work type, posting date, and companies.MIT
TDQS
Scored across 3 tools
Each tool has a distinct responsibility: searching live jobs, listing supported ATS integrations, and resolving company names/URLs to provider-slug pairs. There is no overlap or ambiguity between them.
All three tools use a consistent snake_case verb-first pattern: search_jobs, list_supported_ats, resolve_company. The naming clearly signals action and object.
Three tools is an appropriate size for this server's focused purpose. Each tool is necessary and contributes a distinct step in the workflow from company name to actual job postings.
The tool set covers the full intended workflow: discover supported ATS platforms, resolve a company to the expected identifier, then search live job postings. No obvious missing operations or dead ends are apparent for the stated purpose.