Home · Setup · Claude Code
Resumes and cover letters as Word files, from one stored profile. It keeps one structured profile, writes the resume as .docx trimmed to a page budget with the posting's keywords bolded where you actually have them, drafts a one-page cover letter whose every proof line is a verbatim bullet from that profile, and reports the gaps against a job description instead of filling them in.
The apply_to_job prompt chains the gap analysis, the resume and the letter against one posting in a single turn, and reporting the gaps back at you rather than filling them in is easier to read in a terminal than in a chat bubble.
| You say | Tool |
|---|---|
| Here is my CV: Ada Rowe, backend engineer, Acme Pay since 2021. | profile_set |
| How well do I match this posting? | tailor_to_job |
| Make me a one-page resume for this role and write the letter, direct tone. | resume_create then cover_letter_create |
There is no page-layout engine in pure JavaScript, so trimming runs on a word budget: 450 words of body text per A4 page, 540 in the compact style. Every role keeps its first bullet before any role gets a second, and every bullet dropped is named in the response.
The file is .mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| local (default) | ~/.claude.json, this project only |
| project | .mcp.json at the repository root |
| user | ~/.claude.json, every project |
claude mcp add resume -- npx -y @theluckystrike/mcp-resume
claude mcp list # health-check it before the first prompt
# or --scope project, committed to .mcp.json for the team
No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.
The npm publish of @theluckystrike/mcp-resume is pending; until then use the .mcpb bundle or a clone and build from the latest release.
There is no hosted endpoint for this one yet. MCP Resume and Cover Letter runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Three of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP: time-tracker, price-tracker and invoice.
The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.
Free: profile, the modern style, markdown and HTML exports, 3 cover letters a month, postings up to 2,000 characters. Pro is $19 once, verified offline.
Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.
Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.
Not yet. MCP Resume and Cover Letter runs locally over stdio, which is also how it reads and writes files on your disk. The hosted endpoints at https://mcp.zovo.one/mcp currently cover time-tracker, price-tracker and invoice.
MCP Resume and Cover Letter in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs