Resume-Tailor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RESUME_STORE_PATH | No | Where the master CV JSON lives. Exports go to exports/ next to it. | ~/.resume-mcp/master.json |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_master_resumeA | Store or update the user's base CV so it persists between sessions. Provide the CV as structured JSON. Recommended keys: contact - {name, email, phone, location, links} summary - short professional summary (string) experience - list of {title, company, location, start, end, bullets[]} projects - list of {name, description, tech[], link} skills - list of strings (or {category, items[]}) education - list of {degree, school, location, start, end, details} This is step 1 of the flow: set it up once, reuse it for every job. Returns a confirmation with the stored path. |
| load_master_resumeA | Return the stored master CV so Claude can tailor it to a job. This is the starting point of every tailoring session. If no resume is stored yet, raises a clear error telling the user to save one first. |
| fetch_job_postingA | Get a job posting as clean readable text. Pass a Returns {source, text, char_count}. |
| extract_keywordsA | Pull the skills/tools/keywords an ATS would scan for from a job posting. Deterministic (no ML): tokenizes the text, filters filler words, recognizes known skills and multi-word phrases (e.g. "REST APIs"), and ranks by frequency — boosting terms that appear in skills/requirements sections. Returns {keywords: [ranked strings], detail: [{keyword, score, known_skill}]}. Use the ranked keyword list as input to ats_gap_check. |
| ats_gap_checkA | Compare a CV against job keywords → match score (%) + missing terms. This is the tool's killer feature: it tells the user concretely what to add. Pass the resume as plain text and the ranked keyword list from extract_keywords. Returns which keywords are present, which are missing, and a match percentage — so Claude knows exactly what to surface in the rewrite. Returns {match_score, matched, missing, total_keywords}. |
| export_resumeA | Render finished CV content to a clean, ATS-safe PDF or DOCX file. Pass Returns {path, format, blocks} with the saved file path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/NmaaAlhawary/MCP-Resume-Tailor'
If you have feedback or need assistance with the MCP directory API, please join our Discord server