Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RESUME_STORE_PATHNoWhere the master CV JSON lives. Exports go to exports/ next to it.~/.resume-mcp/master.json

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 url to fetch and strip a posting to plain text, OR pass pasted_text directly if you already have the description. URL fetching is best-effort: if the site is blocked or login-walled, this returns a clear message asking the user to paste the text instead — it never fails silently.

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 content as either markdown text (use #/##/### headings and - bullets) OR structured CV JSON (same shape as the master resume). Choose format = "pdf" or "docx". The layout is deliberately single-column with standard fonts and real text (never image-rendered) so ATS parsers read it.

Returns {path, format, blocks} with the saved file path.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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