Skip to main content
Glama
ailenshen

resume-markdown-mcp

by ailenshen
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

resume-markdown-mcp

Write your resume in Markdown, export to PDF — powered by AI via MCP.

Resume preview

Let Claude write, edit, and format your resume. The MCP server handles Markdown-to-PDF conversion with a built-in stylesheet — no CSS knowledge required.

Requirements: Python ≥ 3.12, Google Chrome or Chromium (for PDF export)

Installation

As an MCP server (recommended)

Add to Claude Code with one command:

claude mcp add resume-markdown -- uvx resume-markdown-mcp@latest

For Claude Desktop, add to claude_desktop_config.json:

{
  "mcpServers": {
    "resume-markdown": {
      "command": "uvx",
      "args": ["resume-markdown-mcp@latest"]
    }
  }
}

As a CLI tool

# Install globally with uv
uv tool install resume-markdown-mcp

# Or with pip
pip install resume-markdown-mcp

Related MCP server: Resume Generator MCP Server

MCP Tools & Resources

Type

Name

Description

Tool

export_resume_pdf

Convert a Markdown resume to PDF. Accepts a file path or raw Markdown text. CSS is applied automatically.

Resource

resume://template

The built-in Markdown resume template. AI reads this to understand the required format.

Resource

resume://style

The built-in CSS stylesheet. AI reads this when you want to customise the appearance.

Example Prompts

  • "Help me write a resume for a software engineer role and export it as a PDF to my Desktop"

  • "Here's my resume at ~/resume.md — export it to PDF"

  • "My resume.md doesn't follow the right format, fix it and export to /tmp/resume.pdf"

  • "Make the font size smaller, save the custom CSS to ~/resume.css, and re-export"

Resume Markdown Format

The PDF renderer depends on these Markdown conventions:

# Full Name

- email@example.com
- Phone number
- City, Country

One-line summary (optional)

## Experience

### <span>Job Title, Company</span> <span>2022 – 2025</span>

- Achievement one
- Achievement two

## Education

### <span>Degree, University</span> <span>2018 – 2022</span>

## Skills

- Skill category: item, item, item

The <span> tags inside ### headings are required — they enable the left/right flexbox layout for title and date. AI handles this automatically when writing from scratch; if your existing file lacks them, ask Claude to reformat it before exporting.

CLI Usage

# Create template files (resume.md + resume.css) in the current directory
resume-markdown-mcp init

# Build HTML and PDF from resume.md
resume-markdown-mcp build

# Options
resume-markdown-mcp build --no-pdf          # HTML only
resume-markdown-mcp build --no-html         # PDF only
resume-markdown-mcp build myresume.md       # Custom input file
resume-markdown-mcp build --chrome-path=... # Specify Chrome path

If a resume.css file exists alongside the input file, it is used automatically; otherwise the built-in stylesheet is applied.

You can also run without installing via uvx:

uvx resume-markdown-mcp@latest init
uvx resume-markdown-mcp@latest build resume.md

Customising the Style

For iterative CSS editing, ask Claude to save the stylesheet to a local file:

"Increase the font size and save the custom CSS to ~/resume.css, then export"

Future exports can reference the same file without re-sending the CSS:

"Re-export my resume using ~/resume.css"

You can also edit ~/resume.css directly in any text editor between exports.

How It Works

  1. AI calls export_resume_pdf with Markdown content or a file path

  2. The server converts Markdown to HTML using python-markdown, with the built-in CSS inlined

  3. Headless Chrome renders the HTML and prints it to PDF

  4. Chrome exits as soon as the PDF is written; the tool returns the output path

License

MIT

Available Tools

1 tool
export_resume_pdfA

Export a Markdown resume to PDF.

Resume Markdown format

The resume must use these conventions for the PDF to render correctly:

  • # Full Name — first h1 becomes the page title and name header

  • Unordered list immediately after h1 — becomes an inline contact bar (email, phone, URL, location)

  • Paragraph after the contact list — optional summary/objective

  • ## Section Name — major section headings (Experience, Education, Skills, etc.)

  • ### <span>Job Title, Company</span> <span>Start – End</span> — entry headings; the two <span> tags are required so the title and dates are laid out left/right via flexbox

  • Bullet lists under an entry — achievements and details

When to use file_path vs markdown_content

  • If the user's Markdown file already follows the format above → pass file_path directly.

  • If the file doesn't follow the format (missing <span> tags, wrong structure, etc.) → read the file, rewrite it to match the format, and pass the result as markdown_content.

  • If you are generating a resume from scratch → write the Markdown and pass as markdown_content.

  • If you need a full example of the correct format → read the resume://template resource first.

CSS / styling

By default the built-in stylesheet is applied automatically — no CSS parameter needed. If the user wants to customise the style:

  • Recommended for iterative editing: read resume://style, modify it, save to a local file (e.g. ~/resume.css), then pass css_path pointing to that file. This way the user can tweak the CSS manually between exports without re-sending it, and future exports just reference the same path with no extra tokens.

  • Pass css_content with the raw CSS text — convenient for one-off changes. To see the default stylesheet, read the resume://style resource.

Parameters

  • markdown_content: Raw Markdown text of the resume (mutually exclusive with file_path)

  • file_path: Path to a .md file (mutually exclusive with markdown_content)

  • css_content: Custom CSS text (mutually exclusive with css_path; optional)

  • css_path: Path to a custom CSS file (mutually exclusive with css_content; optional)

  • output_path: Where to write the PDF (default: ~/resume.pdf)

Returns

JSON string: {"pdf_path": "/absolute/path/to/resume.pdf", "success": true}

ParametersJSON Schema
NameRequiredDescriptionDefault
markdown_contentNo
file_pathNo
css_contentNo
css_pathNo
output_pathNo~/resume.pdf

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, but the description fully covers behavior: expected markdown format, output as JSON, file writing via output_path, and CSS customization options. It explains the internal rendering requirements (e.g., <span> tags) and the return structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections and bullet points, but slightly verbose. Could be trimmed slightly without losing clarity, but it remains readable and front-loads the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no sibling tools, the description is exhaustive: covers markdown format, parameter usage, CSS customization, output specification, and examples. It leaves no significant gaps for an agent to misuse.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet the description explains each parameter's purpose, mutual exclusivity (content vs path), defaults, and relationship to tool behavior. Adds substantial meaning beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool exports a Markdown resume to PDF, specifies the required Markdown format, and differentiates between input methods. It leaves no ambiguity about the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use file_path vs markdown_content, how to handle malformed markdown, and how to customize CSS. Includes concrete examples like reading the template for correct format.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity. The tool's purpose is singular and clearly defined: export a Markdown resume to PDF.

Naming Consistency5/5

The single tool name 'export_resume_pdf' follows a consistent verb_noun pattern, which is clear and descriptive.

Tool Count5/5

One tool is perfectly appropriate for a server that only handles PDF export of Markdown resumes. The scope is narrow and well-defined.

Completeness5/5

The tool set is complete for its stated purpose: exporting a Markdown resume to PDF. Any additional functionality (e.g., reading templates) is provided via resources, not tools.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

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/ailenshen/resume-markdown-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server