mcp-job-search
Related Servers
Alternatives to mcp-job-search
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables Claude to parse CVs, search job boards (Remotive, Arbeitnow, Adzuna, Greenhouse/Lever), tailor resumes and cover letters, and prepare application packages with direct apply links—without ever auto-submitting. It runs 100% locally and free, storing jobs and applications as JSON files.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to discover postings from watched company boards ranked by keyword fit, tailor and fact-check resumes against a source-cited profile, render ATS-readable PDFs, submit applications through the user's own browser, and track replies and follow-ups. All ranking, claim checking and email classification run as plain code, so LLM tokens are spent only on writing.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceExposes the entire job-search workflow as 13 chat-driven tools, letting users refresh a ranked feed of live postings from employers' public hiring APIs, view and score job descriptions, tailor and render truthful one-page LaTeX resumes, review skill gaps and screening answers, and log applications. It keeps a human in the loop, since nothing is ever submitted automatically.MIT
- AlicenseBqualityBmaintenanceEnables Claude Desktop, Cursor, or any MCP client to search six job portals, score CV-to-posting fit with ATS-style gates, tailor resumes and cover letters, export Word documents, and track applications locally.9MIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to store a job-search profile locally, find public job-board postings, evaluate and rank them against the profile, and track seen, saved, applied, or dismissed jobs.MIT
- AlicenseNot gradedqualityBmaintenanceEnables job seekers to structure job descriptions, search a personal Markdown profile with hybrid BM25/dense retrieval, and compare a posting against that profile to see which requirements are supported, weak, or missing evidence. It also tracks applications and follow-up deadlines through JSON-backed tools whose writes stay as previews until a human turn confirms them.MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct action: search_jobs queries APIs while fetch_job_posting grabs one known URL, the three registry tools map cleanly to create/read/update, and lint_cv vs render_pdf are separate phases. The only mild overlap is search_jobs vs fetch_job_posting (both job-finding), but the descriptions explicitly draw the boundary.
All seven tools follow a consistent snake_case verb_noun pattern (fetch_job_posting, lint_cv, log_application, list_applications, update_application_status, render_pdf, search_jobs). No camelCase or stylistic drift.
Seven tools is well-scoped for a job-search assistant covering search, capture, CV lint/render, and an application registry. Each tool earns its place with no redundant entries.
The workflow is largely covered: find jobs, fetch postings, lint and render a CV, and log/list/update applications. Gaps remain in registry lifecycle — no delete/remove row and no way to edit free-text fields beyond status — but these are minor workarounds.