Skip to main content
Glama

career-mcp

An MCP server for the job-search loop: store a resume, drop in a job description, get a real match analysis, a tailored resume and cover letter (exported to PDF), a LinkedIn About section — plus a structured interview that captures your career stories so they're ready to reuse.

Local-first. Your resume and stories live in a folder on your machine (~/.career-mcp by default) — nothing is uploaded anywhere.

How it works

The MCP server itself doesn't call any LLM. It's a data layer: it stores your resume, job descriptions, voice profile, and stories, and hands them back as context. The actual reasoning — match analysis, tailoring, writing — is done by whatever MCP-capable client you're using (Claude Code, Claude Desktop, etc.), the same way any tool-using conversation works.

If you don't have an MCP client, the bundled CLI (career-mcp-cli) does the same job standalone, using your own Groq or Gemini API key (both have usable free tiers) to do the reasoning itself.

Related MCP server: LAPRAS MCP Server

Install

npm install -g @sindhujaks/career-mcp

Add to your client's MCP config (e.g. .mcp.json for Claude Code):

{
  "mcpServers": {
    "career-mcp": {
      "command": "career-mcp"
    }
  }
}

Then, in conversation: save your resume, save a JD, and ask your client to run a match analysis, draft a tailored resume, write a cover letter, or draft a LinkedIn About. Say "let's capture a career story" to run the guided interview.

Tools

Tool

Purpose

save_resume / get_resume

Store/retrieve your base resume

save_voice_profile / get_voice_profile

Store tone/style guidance so generated content sounds like you

save_jd

Store a job description, sets it as the active application

get_active_application

Bundles resume + JD + voice profile + relevant stories as context

list_applications

List all stored applications

save_output

Persist a generated match analysis / resume / cover letter / About section

export_pdf

Render a tailored resume, cover letter, or base resume to PDF (themes: navy, minimal, classic; page size: letter or a4)

save_story / query_stories

Save/retrieve career stories, filterable by tag

start_story_interview / answer_story_question

Guided, protocol-driven interview to capture one new story

PDF export

export_pdf turns a saved markdown resume or cover letter into a PDF that ATS systems can read (real, selectable text — not an image).

  • Uses the browser you already have. It drives your installed Chrome, Edge, Chromium, or Brave in the background — nothing extra is downloaded. If yours lives somewhere unusual, set CAREER_MCP_CHROME_PATH. If no browser is found, you get an .html file instead: open it and use Print → Save as PDF.

  • Works offline. Fonts are bundled with the package.

  • Three themes: navy (default — modern sans-serif, navy accents), minimal (monochrome, compact), classic (serif, centered header).

  • Letter or A4. Defaults to Letter; set CAREER_MCP_PAGE_SIZE=a4 to change the default.

  • Cover letters only on request — the default document is the tailored resume.

The PDF is written next to the markdown (e.g. outputs/tailored_resume.pdf). The markdown stays the source of truth: edit it, then export again.

Resumes render best in this shape (the MCP client is told this automatically):

# Full Name
Target title · positioning
City · email · phone · linkedin.com/in/you

## Summary
...

## Experience
### Job Title — Company
*2021 – Present | City*
- Achievement bullet

Use standalone (no MCP client)

cp .env.example .env   # fill in CAREER_MCP_API_KEY (free Groq or Gemini key)

career-mcp-cli set-resume --file resume.txt
career-mcp-cli set-jd --company Acme --role "Senior Engineer" --file jd.txt
career-mcp-cli analyze
career-mcp-cli resume                         # also writes the PDF
career-mcp-cli cover-letter --pdf             # --pdf is optional
career-mcp-cli pdf --theme classic --page-size a4
career-mcp-cli about
career-mcp-cli interview   # guided story capture

Data layout

~/.career-mcp/
├── resume.json
├── voice_profile.md
├── stories/<slug>.md
└── applications/<company-role>/
    ├── jd.json
    └── outputs/{match_analysis,tailored_resume,cover_letter,linkedin_about}.md
        (+ tailored_resume.pdf / cover_letter.pdf once exported)

Override the location with CAREER_MCP_DATA_DIR.

License

MIT

Available Tools

13 tools
answer_story_questionA

Submit the user's answer to the current interview question and get the next one (or the completed, saved story).

Inputs: answer (required), session_id (required).

export_pdfA

Render a saved markdown document to a PDF that ATS systems can read, using the user's installed Chrome/Edge/Chromium/Brave. Defaults to the active application's tailored resume. Only export a cover letter when the user asks for one. If no browser is found, an HTML file is written instead and the reason is returned — relay it to the user.

Inputs: theme, document, page_size, application_slug.

get_active_applicationA

Returns the stored resume, voice profile, and the active job description together, as context for match analysis or content generation. Use this to: (1) run match analysis — identify genuine overlaps and honest gaps between the resume and JD, not keyword stuffing; (2) draft a tailored resume by reordering/reframing existing resume content for relevance, never fabricating experience; (3) draft a cover letter; (4) draft a LinkedIn About section. Match the voice profile's tone if one is set. Save any generated output with save_output.

Write the tailored resume as markdown in this exact shape so it renders cleanly to PDF:

Full Name

One-line tagline (target title / positioning) Contact line: City · email · phone · linkedin.com/in/... (one paragraph)

Summary (then a short paragraph)

Experience

Job Title — Company

Start – End | Location

  • achievement bullets

Skills (bullets, or a two-column table: | Area | Skills |)

Education

Output only the resume itself — no commentary before or after it.

Inputs: no named parameters.

get_resumeB

Retrieve the stored base resume.

Inputs: no named parameters.

get_voice_profileB

Retrieve the stored voice profile, if one has been saved.

Inputs: no named parameters.

list_applicationsA

List all stored applications (company, role, created date).

Inputs: no named parameters.

query_storiesA

Retrieve saved career stories, optionally filtered by tag (e.g. leadership, conflict, failure-recovery, technical-deep-dive). Use to find a story relevant to a JD requirement, an interview-prep question, or a LinkedIn post idea.

Inputs: tags.

save_jdB

Store a job description for a company/role and mark it as the active application. Creates a new application record. Provide exactly one of jd_text or jd_path.

Inputs: role (required), company (required), jd_path, jd_text.

save_outputA

Persist generated content (match analysis, tailored resume, cover letter, or LinkedIn About draft) for an application. Defaults to the active application if application_slug is omitted. After saving a tailored resume, offer to export it with export_pdf.

Inputs: content (required), output_type (required), application_slug.

save_resumeA

Store the user's base resume, either as raw text or by reading a local file. Overwrites any previously stored resume. Provide exactly one of resume_text or resume_path.

Inputs: resume_path, resume_text.

save_storyA

Save a career story directly (title, tags, content) without running the interview flow. Prefer start_story_interview for a guided capture.

Inputs: tags (required), title (required), content (required).

save_voice_profileB

Store a description of the user's writing voice/tone (e.g. tone attributes, phrases to avoid, sample posts). Used to keep generated cover letters and LinkedIn About sections sounding like the user, not generic AI copy.

Inputs: voice_text (required).

start_story_interviewA

Begin a structured interview to capture one new career story. Returns the first question and a session_id. Keep calling answer_story_question with that session_id, relaying each returned question to the user verbatim, until status is 'complete' — the story is then auto-saved.

Inputs: no named parameters.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: pair-wise get/save for resume and voice profile, a separate story-interview flow (start/answer/query/save), and an output pipeline (save_output/export_pdf). The only real overlap is get_active_application, which re-returns the resume and voice profile already exposed by get_resume/get_voice_profile, so an agent must infer that the aggregate is for generation/analysis context rather than plain retrieval.

    Naming Consistency5/5

    Every name follows a consistent snake_case verb_noun pattern (get_resume, save_jd, list_applications, query_stories, export_pdf), with no camelCase or style mixing. The story-interview trio (start_story_interview, answer_story_question, save_story) reads as a coherent family.

    Tool Count5/5

    Thirteen tools is well within a comfortable range for a multi-stage workflow (resume, voice, JD, stories, generation, export). Each tool maps to a distinct step and none look like filler.

    Completeness3/5

    The write/read pairs and generation+export pipeline cover the main path, but the application lifecycle is thin: there is no update/get/delete for an application record (no status tracking, no switching active application other than by saving a new JD), and no way to list or retrieve previously saved outputs beyond export_pdf for the tailored resume. Agents will hit dead ends when managing multiple applications or reviewing saved drafts.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      CareerMate is an MCP-first, local-only career management tool that stores your career data (profiles, resumes, cover letters, job postings, applications, interview prep) on your computer and exposes it through MCP tools for AI agents to read and write.
      16 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to search job listings, view job details, and retrieve or update work experiences, job summaries, career goals, and technical skills through natural language.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search job listings and retrieve or update a user's career profile, including work experiences, job summaries, career goals, and technical skills through natural language.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables job searching and management of career profile data such as experiences, job summaries, career goals, and technical skills through natural language.
      -