Skip to main content
Glama
resume-kit-mcp

resume-kit-mcp

resume-kit

Tailored resume versions from one fact library, with guardrails that keep them honest.

resume-kit demo: a draft from a posting, a guardrail failing the build, a page-target check, a scored gap

You keep every confirmed fact about your career in one file. Each job gets a short version file that picks and orders those facts, with its own headline and summary. resume-kit renders a version to .docx and .pdf, checks that it hits your page target, and won't build anything that breaks one of your guardrails: claims you've ruled out, or facts that must always appear. It can also score a version against a job posting with shortlist-ai, the way a screener would read it. All of this is also an MCP server, so an AI assistant can tailor, build, and score resumes for you without making things up.

Why

Tailoring a resume for every job tends to produce a dozen near-copies that drift apart. A number gets corrected in one copy but not the others. A claim you walked back reappears. Page 3 appears without anyone noticing. With resume-kit:

  • Each fact lives in one place. Versions refer to facts by id and never restate them, so a correction reaches every version.

  • Guardrails fail the build. guardrails.yaml lists claims that must never appear (with the reason) and facts that must. They're checked on every build, which also makes it safe to let an AI assistant write versions.

  • The page count is checked. The build fails unless the PDF hits its target, and it prints the text that spilled over.

  • Gaps get sorted. resume score lists the must-haves a posting asks for that the resume doesn't show. A gap that matches a guardrail is labeled as a real gap, not a wording problem to paper over.

Related MCP server: WebMCP

Setup

git clone https://github.com/vinayvobbili/resume-kit && cd resume-kit
python3 -m venv .venv && .venv/bin/pip install -e '.[dev]'
npm install                                          # docx-js, used by the renderer
brew install --cask libreoffice && brew install poppler   # PDF conversion and page checks

Try it on the bundled example (a fictional candidate):

resume --content examples/content build --all --out /tmp/resumes

Your content

Content lives outside this repo, so your personal data never ends up in it:

cp -R examples/content ~/resume-content                 # then replace the facts with yours
mkdir -p ~/.config/resume-kit && ln -s ~/resume-content ~/.config/resume-kit/content

resume-kit looks in the --content flag, then $RESUME_KIT_CONTENT, then ~/.config/resume-kit/content, and falls back to the example (and says so). Keep answers.yaml out of version control.

Commands

resume list                         # versions, the content dir in use, and applied dates
resume draft acme-sre posting.md    # draft a tailored version from a posting
resume check                        # guardrails on every version
resume build acme --preview         # -> ~/Downloads/<output>.{docx,pdf}
resume score acme                   # score against the version's posting

show, diff, facts, trace, answers and ats are in the guide, along with the options a version can set (extends, drop, undated, waive, copy_to and more), how drafting and since: guardrails work, scoring backends, the MCP tools and the ATS notes.

MCP server

claude mcp add resume-kit -s user -- /path/to/resume-kit/.venv/bin/resume-kit-mcp

Its instructions tell the assistant never to add unconfirmed facts, and never to "close" a gap that a guardrail marks as real.

Tests

pytest -m "not render" is fast; pytest also renders the examples. scripts/check runs what CI runs. Tests only use the fictional example content.

License

MIT

Available Tools

7 tools
application_answersB

Standard answers for application forms: contact, work_authorization, experience_years, screening, salary, defaults, eeo. Omit section for everything.

Inputs: section.

ats_playbookC

Quirks, shared rules, and JavaScript helpers for an applicant tracking system (greenhouse, ashby, taleo, workday, linkedin, eightfold) or a job-page host.

Inputs: system (required).

build_versionC

Render .docx and .pdf (default ~/Downloads), check the page target, report overflow text.

Inputs: version (required), out_dir, with_preview.

check_factsC

Run the fact guardrails (forbidden claims, required facts) on one version or all of them.

Inputs: version.

list_versionsB

List resume versions with their title and applied date, and the content directory in use.

Inputs: no named parameters.

score_versionA

Score the built resume against job postings (file paths; default: the version's posting) with shortlist-ai. Returns per-job score, must-haves met, gaps, and per-requirement verdicts with quotes. gap_notes marks gaps that a guardrail says are real, which must not be papered over.

Inputs: version (required), backend, postings.

show_versionD

The resolved resume as plain text (what the PDF will say).

Inputs: version (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      15 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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