Home · Setup · Claude Desktop
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.
A job application is the one thing on this list you do outside a repository, in the evening, in the client you already have open. Give an absolute path when you ask it to read your old resume, and open the .docx it hands back from Finder without leaving the window.
| 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 claude_desktop_config.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
{
"mcpServers": {
"resume": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-resume"]
}
}
}If node came from nvm, asdf or homebrew, replace "npx" with the absolute path that which npx prints:
"command": "/Users/you/.nvm/versions/node/v22.14.0/bin/npx"Save, then completely quit Claude Desktop and start it again. A window reload is not enough.
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.
Two documented facts decide whether the entry works: every path in claude_desktop_config.json must be absolute, and a stdio server started here inherits only a limited, platform-dependent subset of environment variables. If node came from nvm or homebrew, paste what `which npx` prints instead of the bare word. The .mcpb route avoids both: Claude Desktop ships a built-in Node.js environment.
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.
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. There is no published Linux path. Settings, Developer, Edit Config opens the right copy and creates it if it does not exist.
In order: did you fully quit and restart, not just close the window? Is every path absolute? And is the command resolvable, given the limited environment a stdio server inherits here? If node came from nvm, paste what which npx prints.
Yes. An .mcpb bundle, the format renamed from .dxt, opens with Claude and shows an installation dialog. One you built yourself goes in through Settings, Extensions, Advanced settings, Install Extension.
MCP Resume and Cover Letter in detail · The same server in Cline and Claude Code · Every server in Claude Desktop · Guides · Claude Desktop docs