Everything below is about using DraftShelf itself. If you can't find your answer, email us directly and we'll get back to you.
From a real, signed-in walkthrough - everything from your first sign-in to tailoring one resume for two different roles.
Sign up with an email and password, or with Google or GitHub. Every account is fully free, and everything you enter is private to you.
Every tailored resume you build lives here as its own card. A brand-new account starts empty - click "+ New version" whenever you're ready for your first one.
The Library tab is where every job, project, school, and skill you've ever had lives - add it once here. Each entry can hold several bullet points, and you'll pick which ones to use per resume later.
Open a version, check off which Library entries and bullets belong on this particular resume, and watch the preview on the right update live. When it looks right, click Download PDF or Download DOCX in the top-right corner.
Tag bullets with a role name (e.g. data-analyst, business-analyst)
in the Library, then use Fill in with tag at the top of any version to pull in
everything tagged for that role at once - it only adds or switches content, it never removes
anything you've already included, and it asks before making any change.
Click Edit details on any checklist item to open, edit, and add bullets to that Library entry right from the editor. The Save changes to choice at the bottom decides how far the edit reaches: update the shared Library everywhere it's used, keep it local to just this one version, or pick per version.
Let Claude Code, Codex, Claude Desktop, claude.ai, or ChatGPT read and edit your Library and Versions directly, right from the conversation.
A coding tool running on your own machine.
claude mcp add draftshelf -s user -- npx -y draftshelf-mcp
codex mcp add draftshelf -- npx -y draftshelf-mcp
Claude Desktop also supports Connectors directly (see that column) - use this config file instead for any tool with no Connectors option of its own:
{
"mcpServers": {
"draftshelf": {
"command": "npx",
"args": ["-y", "draftshelf-mcp"]
}
}
}
The first time it actually launches the server, your browser opens on its own to a real DraftShelf sign-in + consent screen - sign in there once, then ask it something like "add a bullet to my most recent experience entry" and reload DraftShelf in your own browser to confirm the change is really there. Every launch after that is instant, no browser involved - if your tool gives up before you finish signing in, finish anyway and just ask it to try again.
The full setup guide lives on the draftshelf-mcp npm package page.
Add DraftShelf as a connector directly in the chat interface - nothing runs on your own machine.
Go to Settings → Connectors, click the + button, then Add custom connector (same steps on both). Paste in:
https://mcp.draftshelf.app
Click Add, sign in (or create an account), and click Allow when asked to connect. Free, Pro, and Max accounts can add it directly (Free is limited to one custom connector); on a Team/Enterprise account, an organization owner adds it once under Organization Settings → Connectors, and members then enable it individually.
Open Settings → Security and login and turn on Developer mode (this feature is currently only available that way). Then go to Plugins, click the + button, and paste in:
https://mcp.draftshelf.app
Sign in and approve the connection.
Ask it something like "add a bullet to my most recent experience entry" and reload DraftShelf in your browser to confirm the change is really there. Every write it makes goes through the same validated, revision-checked path a browser edit does, and if GitHub backup is connected, it fires from there too - reopening the same chat later needs no re-sign-in, and Claude Desktop's own Connectors screen works exactly the same way as claude.ai's shown above.
Disconnect any time from Settings → Connected Apps in DraftShelf.
Short answers to the questions we hear most.
Common snags and how to clear them.
Terms used throughout the app.
DraftShelf is an independently run tool, not a company with a support team - email is genuinely the fastest way to reach a real person.
For questions, bug reports, or feedback on this help page itself:
ariadaikalam1234@gmail.com
If something feels broken (PDF export failing, changes not saving), check whether it's a known server issue: Status page