JobOK MCP
Related Servers
Alternatives to JobOK MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables LLM clients to analyse job postings, tailor resumes from an evidence-labelled profile, validate every claim against that profile, and track applications, all through deterministic MCP tools.7Apache 2.0
- AlicenseAqualityBmaintenanceEnables MCP clients such as Claude Desktop or compatible editors to run local, privacy-first job-search workflows including resume generation and STAR polishing, JD matching, GitHub project recommendations, mock interviews, and application tracking. It exposes these capabilities as callable tools through the Model Context Protocol.71MIT
- AlicenseNot gradedqualityAmaintenanceA local-first, open-source MCP server that analyzes jobs, matches your CV, tailors documents, and tracks applications — all on your machine with no data uploaded.AGPL 3.0
- FlicenseAqualityCmaintenanceEnables searching job listings, tracking applications, managing resumes, and tailoring resumes to job posts, all locally via MCP.620-
- AlicenseNot gradedqualityBmaintenanceEnables an MCP-capable coding agent to run a local-first job search: recording verified opportunities in a private SQLite tracker, tracking follow-ups and outcomes, and preparing evidence-based resumes, application answers, and outreach drafts. It keeps all personal data on the user's machine and stops before submitting applications, uploading documents, or contacting anyone.1MIT
- AlicenseNot gradedqualityDmaintenanceAn intelligent, zero-cost MCP server that securely parses local resumes and compares them against live job postings for ATS scoring, skill gap analysis, and interview prep.MIT
TDQS
Scored across 40 tools
Most tools have distinct resource+action purposes (e.g. resume_rewrite vs ats_optimize vs gap_analysis), but there are four exact duplicate/alias pairs (job_score_match≈resume_score_match, generate_interview_question≈interview_question_bank, add_application_record≈application_add, interview_summary≈interview_review) that an agent could easily misselect. Overlapping clusters like scoring/gap/ATS and application_stats vs job_search_review add mild confusion.
The dominant pattern is resource_action snake_case (strength_save, application_add, job_archive_list), which is readable, but it is mixed with bare noun phrases (gap_analysis, analysis_history, data_info, interview_question_bank) and the four legacy tools use reversed verb_noun style (generate_interview_question, add_application_record). Conventions are inconsistent across the set.
40 tools is well above the heavy threshold for a single assistant, and the count is unnecessarily inflated by four deprecated alias tools that duplicate existing functionality. Even across the broad domains (profile, resume, interview, strengths, applications, archive, analysis), the surface feels over-large rather than tightly scoped.
Coverage is strong: full CRUD on applications and strengths, resume lifecycle (load/get/score/rewrite/ATS/export), interview question bank and mock sessions, archive with conversion to applications, plus gap analysis, learning paths, review, and data export. Only minor gaps remain (no profile or resume delete), which agents can work around.