ResumePilot MCP

ResumePilot MCP

Enables parsing a master resume, analyzing job descriptions for ATS/match scores, generating truthful tailored resumes, tracking applications, and producing PDF reports through Claude Desktop.

Category
Visit Server

README

ResumePilot MCP

A scalable Universal Job Application MCP server for Claude Desktop.

You give Claude one master resume. ResumePilot then parses it, builds a reusable profile, analyzes job descriptions against it, computes job-specific ATS/match scores, generates tailored resumes that never invent information, tracks every application in a local database, and produces a final PDF report with per-application tracking pages.

Phase 1 (this release) is a complete, tested, fully-local foundation. You paste a job description and the entire pipeline runs end-to-end — no external job site required. Global job search, application automation and email tracking are later phases that slot into the same adapter architecture. See docs/ARCHITECTURE.md.

What it will not do

  • ❌ Never invents skills, experience, education, certifications or metrics.
  • ❌ Never stores LinkedIn/Naukri/other passwords or OTPs.
  • ❌ Never bypasses CAPTCHA, 2FA, bot protection or authentication.
  • ❌ Never auto-submits to arbitrary websites (Phase 1 prepares; you submit).

If a required skill can't be verified from your material, ResumePilot reports "Required skill not verified from the user's profile." — it will not add it.

Requirements

  • Node.js ≥ 18.18
  • Claude Desktop (for MCP usage)

Install & build

git clone <your-fork-url> resumepilot-mcp
cd resumepilot-mcp
npm install
npm run build
cp .env.example .env    # optional — sensible defaults otherwise

Try it without Claude (offline demo)

Runs the full pipeline through the same tools Claude calls, in a temp folder:

npm run demo

You'll see original→optimized ATS scores, a generated PDF report and HTML tracking pages.

Run the tests

npm test

40 tests cover parsing, scoring, the "never invent" guarantee, optimization, tracking, reporting and the end-to-end tool pipeline.

Download (Claude Desktop extension)

Grab the ready-to-install extension from the Releases page:

Download For
resumepilot.mcpb The Claude Desktop extension — works on Windows, macOS and Linux (pure-JavaScript, no native binary). Drag it into Claude Desktop → Settings → Extensions.
install-windows.bat One-click build-from-source installer for Windows.
install-macos.command One-click build-from-source installer for macOS.
install-linux.sh Build-from-source installer for Linux.

Just want the extension? Download resumepilot.mcpb, open Claude Desktop → Settings → Extensions, drag the file in, set your data folder, toggle it On.

Install into Claude Desktop

Two options — full walkthrough in docs/INSTALL.md:

  • One-click Desktop Extension: npm run bundle produces resumepilot.mcpb; drag it into Claude Desktop → Settings → Extensions, set your data folder, toggle On. (The bundle embeds a native SQLite binary, so build it on your own OS — one command — for macOS/Windows.)
  • Manual MCP config: build from source and add a mcpServers entry.

Connect to Claude Desktop (manual config)

  1. Build: npm run build (produces dist/src/index.js).

  2. Open your Claude Desktop config file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
  3. Add the server (see docs/claude_desktop_config.example.json), using absolute paths:

    {
      "mcpServers": {
        "resumepilot": {
          "command": "node",
          "args": ["/ABSOLUTE/PATH/TO/resumepilot-mcp/dist/src/index.js"],
          "env": {
            "RESUMEPILOT_DATA_DIR": "/ABSOLUTE/PATH/TO/your-private-data",
            "ATS_TARGET_SCORE": "90"
          }
        }
      }
    }
    
  4. Fully quit and reopen Claude Desktop. ResumePilot's tools appear under the tools (🔌) menu.

Use it

Just say:

“Start my ResumePilot job application process.”

Claude understands the workflow and will:

  1. Ask for your master resume → upload_master_resume (give it the file path).
  2. Parse it and ask only for missing info → analyze_master_resume → setup_user_profile.
  3. Take a job description you paste → analyze_job (shows original ATS + gaps).
  4. Build a tailored resume → optimize_resume_for_job (original vs optimized ATS, PDF + DOCX).
  5. Prepare the application → generate_application_profile → prepare_application.
  6. Record it → apply_to_job (Phase 1: you submit; Claude marks it APPLIED on your confirmation).
  7. Track it → update_application_tracking / search_application_emails.
  8. Produce the final report → generate_application_report (PDF + tracking pages).

Example prompts

  • "Here's my resume: /Users/me/Documents/resume.pdf. Set up my profile."
  • "Analyze this job against my resume: <paste JD>"
  • "Optimize my resume for application 1 and show me the before/after ATS score."
  • "What changed, and what couldn't you verify?"
  • "Generate my application report."

Configuration (.env)

Variable Default Meaning
RESUMEPILOT_DATA_DIR ./data Where your private data lives (git-ignored)
ATS_TARGET_SCORE 90 Target ATS score (never guaranteed, never stuffed)
MATCH_SCORE_THRESHOLD 60 Min match score to recommend applying
JOB_SEARCH_MAX_JOBS 1000 (Phase 2+) max jobs per run
JOB_SEARCH_CONCURRENCY 10 (Phase 2+) bounded worker concurrency
RESUMEPILOT_LOG_LEVEL info error|warn|info|debug (stderr only)

Security & privacy

  • Your data stays on your machine under RESUMEPILOT_DATA_DIR (git-ignored).
  • No third-party passwords or OTPs are ever stored; future integrations use official OAuth/session flows with tokens kept out of logs.
  • Logs go to stderr only and redact secret-looking values.
  • Delete your data any time by removing the data directory.

Project layout

src/
├── index.ts, server.ts          # MCP stdio server + tool registration
├── context.ts                   # composition root
├── tools/                       # 17 MCP tools (thin, Zod-validated)
├── services/                    # parsing, scoring, optimization, tracking, reports
├── providers/                   # jobs / applications / email adapters (+ registries)
├── database/                    # SQLite schema + repository
├── models/                      # Zod schemas & types
└── utils/                       # config, logger, text/keyword processing, ids
tests/                           # vitest suite (40 tests)
docs/                            # ARCHITECTURE.md, Claude Desktop config
scripts/demo.ts                  # offline end-to-end demo

Roadmap

Phase 2: generic search adapter, worker pool, dedup, ranking, ≤1,000 jobs · Phase 3: supported job-source integrations · Phase 4: application adapters · Phase 5: Gmail tracking (OAuth) · Phase 6: hosted tracking UI + packaging.

License

MIT — see LICENSE.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured