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.
Keep the profile in one place and the postings in another: paste the job text into the chat, read the coverage figure, and let the .docx land in the folder you have open so the version you actually sent is the version on disk.
| 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 .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
{
"mcpServers": {
"resume": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-resume"]
}
}
}The Customize page shows the server and its tools once it has started.
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 current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
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.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Resume and Cover Letter pasting the config block above is the supported route.
MCP Resume and Cover Letter in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs