Unified Jobs MCP Server
Related Servers
Alternatives to Unified Jobs MCP Server
No user-submitted related servers found.
Related Servers
- 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 gradedqualityBmaintenanceEnables natural-language job search and aggregation from multiple recruitment websites with zero configuration, providing filtered results and standardized output for AI assistants.51 npmISC
- 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
- AlicenseAqualityCmaintenanceEnables real-time job search across thousands of companies' open roles from Greenhouse, Lever, Ashby, and SmartRecruiters, with full-text filtering and company-specific queries, no API key required.2MIT
- AlicenseNot gradedqualityCmaintenanceGives AI agents a daily-refreshed index of 350k+ open jobs scraped from 12,000+ company career sites on Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee and Personio. Enables keyword, country, remote, seniority and recency job searches, discovery of roles opened since yesterday, and weekly company hiring-signal rankings, with per-call cost caps.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
TDQS
Scored across 4 tools
search_unified_jobs and search_hn_hiring overlap substantially: the unified tool already covers the HN thread as a source, so the dedicated HN tool is largely a subset of the general one. The descriptions do explain the difference (HN-only, no company list, whole thread), which keeps it usable, but an agent must read carefully to avoid redundant calls. list_sources and get_premium_access are clearly distinct from the search tools and from each other.
All four names follow a clean verb_noun snake_case pattern: search_unified_jobs, search_hn_hiring, list_sources, get_premium_access. Verbs (search/list/get) accurately signal the operation type, and there are no style deviations.
Four tools is on the thin side but defensible for a focused read-only job aggregator: two search entry points plus two metadata helpers. Nothing feels gratuitous, though the surface is small enough that a single search endpoint with source filters could arguably replace two.
The surface covers discovery well (cross-source search, HN search, source documentation), but there is no way to fetch a single canonical job record by id, no pagination/cursor continuation tool, and no detail endpoint for a merged record. get_premium_access is an informational upsell rather than a functional capability, which leaves the surface feeling search-only with dead ends after results are returned.