Gives Claude direct, authenticated access to your ResumeAI resumes — list them, read them, tailor one to a job posting, and save it back, all without leaving the chat. No copy-pasting, no AI logic in the server: Claude does the writing, this just reads and saves your data.
Three steps from zero to Claude editing your resume.
In ResumeAI, go to Settings → AI Tools → Create token. You'll see the raw token once — copy it.
Point your MCP client at this deployment's /api/mcp endpoint with your
token as a Bearer header.
"Tailor my Default CV to this job posting" — Claude calls the tools below to fetch, rewrite, and save it.
Nine tools, all scoped to the authenticated caller's own resumes. There is no delete tool — destructive actions stay in the web UI.
Lists the caller's resumes (id, title, template, updated_at) — the usual starting
point to find a resume_id.
Fetches the full record for one resume — content and design settings — before any edit is made.
input: resume_idCreates a new, empty resume seeded from the product defaults.
input: title?Copies an existing resume's content and design into a brand-new resume row.
input: resume_id, new_title?Creates a new resume tailored to a job description, seeded from "Default CV". Also creates a matching Job Tracker entry.
input: data, new_title, source_resume_id?, company_name?, job_role?, job_description?, jd_url?Replaces a resume's complete content — typically after tailoring the summary, experience, and skills to a job description.
input: resume_id, dataReplaces one section (e.g. "experience" or "skills") in place, for a targeted edit instead of a full rewrite.
input: resume_id, section_id, sectionReplaces personal details — name, title, photo, contact fields — without touching the resume's sections.
input: resume_id, personalRenames a resume, leaving its content and design untouched.
input: resume_id, title
Point your MCP client at this server's /api/mcp endpoint and send your own
token as a bearer header — every call is re-validated against it, so revoking a token
in Settings takes effect immediately.
{
"mcpServers": {
"cv-builder": {
"type": "http",
"url": "https://<this-deployment>.vercel.app/api/mcp",
"headers": { "Authorization": "Bearer cvb_xxxxxxxx..." }
}
}
}type/url/headers vs. a
transport block) vary slightly by MCP client — check your client's docs
for its remote-server config shape.