ResumePilot MCP
Enables tracking and searching application-related emails through Gmail using OAuth.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ResumePilot MCP Analyze this job description and tailor my resume for it."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: career-agent
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 otherwiseTry it without Claude (offline demo)
Runs the full pipeline through the same tools Claude calls, in a temp folder:
npm run demoYou'll see original→optimized ATS scores, a generated PDF report and HTML tracking pages.
Run the tests
npm test40 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 |
| The Claude Desktop extension — works on Windows, macOS and Linux (pure-JavaScript, no native binary). Drag it into Claude Desktop → Settings → Extensions. |
| One-click build-from-source installer for Windows. |
| One-click build-from-source installer for macOS. |
| 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 bundleproducesresumepilot.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
mcpServersentry.
Connect to Claude Desktop (manual config)
Build:
npm run build(producesdist/src/index.js).Open your Claude Desktop config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
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" } } } }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:
Ask for your master resume →
upload_master_resume(give it the file path).Parse it and ask only for missing info →
analyze_master_resume→setup_user_profile.Take a job description you paste →
analyze_job(shows original ATS + gaps).Build a tailored resume →
optimize_resume_for_job(original vs optimized ATS, PDF + DOCX).Prepare the application →
generate_application_profile→prepare_application.Record it →
apply_to_job(Phase 1: you submit; Claude marks it APPLIED on your confirmation).Track it →
update_application_tracking/search_application_emails.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 |
|
| Where your private data lives (git-ignored) |
|
| Target ATS score (never guaranteed, never stuffed) |
|
| Min match score to recommend applying |
|
| (Phase 2+) max jobs per run |
|
| (Phase 2+) bounded worker concurrency |
|
|
|
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 demoRoadmap
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.
Available Tools
17 toolsanalyze_jobAnalyze a jobA
Ingest a job (Phase 1: paste the description) and analyze it against the master resume + profile. Extracts structured job info, computes the ORIGINAL ATS/match scores, and identifies missing keywords, buried experience, weak bullets and unverifiable requirements (never invented). Creates a tracked application and returns its number. Follow with optimize_resume_for_job.
Inputs: description (required), url, title, company, +1 more.
analyze_master_resumeAnalyze master resumeA
Parse the stored master resume into structured professional information, build a draft Master Profile, and return the list of missing fields ResumePilot should ask the user about. Nothing is invented.
Inputs: no named parameters.
apply_to_jobApply to jobA
Attempt to submit the application through the resolved application adapter. In Phase 1 the manual adapter never auto-submits to external sites: it returns PAUSED_FOR_USER with a checklist. Pass markApplied: true ONLY after the user confirms they submitted it themselves, to record it as APPLIED.
Inputs: application (required), note, markApplied.
connect_job_sourceConnect a job sourceA
Inspect or connect a job source adapter (professional networks, global/regional job boards, company career pages, public job APIs, supported ATS pages). Phase 1 has the manual source ready. Real search adapters connect via their OFFICIAL login/OAuth in later phases — ResumePilot never stores passwords or OTPs.
Inputs: source.
generate_application_profileGenerate application profileA
Build the job-specific application profile: the reusable fields ResumePilot can safely autofill from the VERIFIED master profile, the known answers, and the questions that must be answered by the user (never guessed — especially legal/declaration answers).
Inputs: application (required).
generate_application_reportGenerate application reportB
Generate the final professional PDF report (summary stats + application table + per-application detail sections) and the local HTML tracking pages (one per application, plus an index). Returns the file paths so the user can open/download them.
Inputs: includeTrackingPages.
get_application_statusGet application statusB
Return the status, scores and timeline of one application (by number) or all applications.
Inputs: application.
get_user_profileGet user profileB
Return the current Master Profile and any still-missing fields.
Inputs: no named parameters.
optimize_resume_for_jobOptimize resume for a jobA
Generate a job-specific tailored resume for a tracked application. Surfaces already-demonstrated keywords, reorders skills/bullets, and adds a role-targeted summary — using ONLY information genuinely present in the master resume/profile. Never invents skills, experience, education or certifications. Produces PDF + DOCX and returns original vs optimized ATS scores, the changes made, and any requirements that could not be verified.
Inputs: application (required), targetScore.
prepare_applicationPrepare applicationA
Prepare everything needed to apply: autofill map, customized resume to attach, and a step-by-step manual checklist. In Phase 1 nothing is auto-submitted to external sites — the application is set to READY_TO_APPLY and any human-only steps (login, CAPTCHA, OTP, 2FA, identity, legal declarations) are listed for the user.
Inputs: application (required).
rank_jobsRank analyzed jobsA
Rank all analyzed applications by overall match score (ATS as tiebreaker) and flag which clear the MATCH_SCORE_THRESHOLD for applying.
Inputs: threshold.
search_application_emailsSearch application emailsB
Search the connected email provider for messages related to an application (by company, role, recruiter email, or domain), classify each into a status (APPLICATION_RECEIVED, SCREENING, INTERVIEW, OFFER, REJECTED, ...), and update the application's tracking. Phase 1 uses an offline mock provider (seed it in tests/demos); Phase 5 connects Gmail via OAuth (read-only, no passwords stored).
Inputs: application (required), since, domain, recruiterEmail.
search_jobsSearch jobsB
Search connected job sources for relevant jobs (up to JOB_SEARCH_MAX_JOBS with JOB_SEARCH_CONCURRENCY workers). In Phase 1 no automated search source is connected yet — paste a job description into analyze_job instead. This tool returns the planned configuration and which sources could serve the query.
Inputs: limit, roles, keywords, workMode, +1 more.
setup_user_profileSet up user profileA
Apply the user's answers to the missing-information questionnaire, merging them into the Master Profile. Pass an answers object keyed by field name (e.g. { fullName, email, phone, location, workAuthorization, workModePreference, noticePeriod, salaryExpectation, preferredRoles }). Only fills provided fields; never overwrites with blanks; never asks twice.
Inputs: answers (required).
update_application_trackingUpdate application trackingB
Manually update an application's tracking: set a new status (with timestamped history) and/or attach an email update. Use to record interviews, offers, rejections, or withdrawals.
Inputs: application (required), note, email, status.
update_user_profileUpdate user profileA
Update specific Master Profile fields with an updates object. Same merge semantics as setup_user_profile. Use for corrections or adding preferences (e.g. preferredLocations, relocationPreference, reusable application answers).
Inputs: updates (required).
upload_master_resumeUpload master resumeA
Register the user's ONE master resume (PDF, DOCX, TXT, or Markdown). Provide either a local file path (preferred — the file is on the user's machine) or raw text. The original is stored immutably and never modified.
Inputs: path, text.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Most tools have clearly distinct purposes, but there is slight overlap between generate_application_profile and prepare_application (both prepare components for applying) and between search_application_emails and update_application_tracking (both can update status). Descriptions clarify boundaries, but a few tools could be confused without careful reading.
All tool names follow a consistent verb_noun or verb_preposition_noun pattern using snake_case. Examples like upload_master_resume, analyze_job, get_application_status, and generate_application_report are predictable and follow the same convention throughout.
At 17 tools, the set is slightly heavy but justified by the broad scope of resume management, job analysis, application preparation, tracking, and reporting. Each tool addresses a distinct step in the workflow, though a few could potentially be consolidated without loss of clarity.
The tool set covers the full lifecycle from resume upload and profile setup, through job analysis and optimization, to application preparation, submission (manual), tracking, email search, and reporting. No critical steps are missing; the only limitation (e.g., no delete or edit for resume) is intentional due to immutability.
Maintenance
Related MCP Connectors
Analyze job listings against your resume, track applications, and generate cover letters.
Your career companion for ATS checks, resumes, cover letters, job tracking, websites, and more.
AI resume triage for recruiters. Query your candidate pool from Claude or ChatGPT.
Build, version and render resumes as PDFs from Claude or any MCP client.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to intelligently query and analyze your resume using RAG technology. Supports skill matching against job requirements and answering questions about your professional background from locally stored resume files.MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to manage a job search end-to-end: find and score job listings, tailor resumes, generate application messages, and track application history, while leaving final external actions to the user.-
- AlicenseAqualityCmaintenanceEnables local ATS-style resume scanning against job postings, providing match rates, missing keywords, and edit suggestions through Claude Desktop.5MIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude Web users to manage their job application workflow by storing profile and resume data, analyzing job descriptions, preparing applications, and tracking progress — all with manual submission and no platform automation.1-