resume-kit-mcp
Related Servers
Alternatives to resume-kit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceTurns any AI assistant into an ATS-optimized resume engine that tailors resumes to job descriptions, validates candidate intake, analyzes gaps, scores matches, and renders DOCX/PDF outputs.9MIT
- AlicenseNot gradedqualityBmaintenanceEnables evidence-grounded resume tailoring by generating ATS-readable LaTeX/PDF resumes from a user-curated experience bank, with every bullet traceable to evidence and inferred wording flagged for user approval.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to tailor a resume to any job description by extracting keywords, analyzing gaps and ATS compliance, managing versions, and compiling PDF/LaTeX outputs entirely locally without external API keys.MIT

Civify MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI agents to parse resumes, tailor CVs, score ATS compatibility, redact PII, scrape job postings, and track applications through a career platform.8348 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to work inside a resume workspace where it can search job postings and propose edits grounded in user-recorded facts, while the interface constrains its tools and requires human approval before any change or application is prepared.9 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to run deterministic job-application workflows—fit-checking job descriptions, generating gap analyses, resumes, cover letters, LinkedIn/GitHub copy, and learning-plan PDFs—while refusing document generation when skill match is below Good.1MIT
TDQS
Scored across 7 tools
Most tools target clearly distinct actions: list_versions (enumerate), show_version (preview text), build_version (render files), check_facts (guardrails), score_version (job matching), application_answers (form data), ats_playbook (reference). There is mild conceptual overlap between show_version/build_version (both produce the resume) and between check_facts/score_version (both validate against requirements), but the descriptions distinguish internal guardrails from external scoring well enough.
Five of seven tools follow a clean verb_noun pattern (list_versions, show_version, check_facts, build_version, score_version). The remaining two (application_answers, ats_playbook) are noun phrases rather than verb-led, a minor deviation that still reads clearly.
Seven tools is well-scoped for a resume-tailoring workflow, and each tool maps to a distinct step (list, preview, validate, build, score, form answers, ATS guidance). No redundant or filler tools.
The surface covers the consume/validate/build/score lifecycle plus application-form and ATS support, which is strong for the stated purpose. The main gap is authoring: there is no create/update/delete for versions or content, so resume editing must happen outside the server (implied by the 'content directory' model), a minor workaround.