job-board-mcp
Related Servers
Alternatives to job-board-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables 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
- 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.-
- AlicenseAqualityDmaintenanceTransforms Claude into an AI job-hunting assistant that searches remote job boards, scores roles against your CV, generates tailored cover letters, and logs everything to a Notion tracker.11MIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude Desktop to manage a job search end-to-end: find and score job listings, tailor resumes, generate application messages, and track application history, while leaving final external actions to the user.-
- AlicenseAqualityDmaintenanceEnables users to manage job applications (add, list, update status) through natural language conversations, using Notion as the backend.3MIT
TDQS
Scored across 3 tools
Each tool maps to a distinct step of a read-only workflow: list_companies enumerates sources, search_jobs queries them, get_job fetches one full description. Descriptions explicitly cross-reference each other (use these names in search_jobs; pass company/job_id to get_job), leaving no plausible misselection.
All three follow a clean verb_noun snake_case pattern (list_companies, search_jobs, get_job). Verb choice is also semantically precise: list for enumeration, search for filtering, get for single-resource retrieval.
Three tools is the minimum viable surface for discover-sources → search → inspect, and each earns its place with no redundancy. Nothing is padded or missing at the operation level.
The read-only lifecycle is fully covered end to end, including error/warning reporting in search results. Minor gaps: no explicit pagination/offset beyond limit, and no batch job-fetch, so an agent must loop on get_job for multiple postings.