resume-pdf-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node environment. Typically production. | |
| TEMP_DIR | No | Directory for per-request workspace/temp files. Default is ./temp. | ./temp |
| LOG_LEVEL | No | Logging level: silent | error | warn | info | debug. Default is info. | info |
| OUTPUT_DIR | No | Directory where generated PDFs/TeX files are saved. Default is ./output. Prefer absolute path in MCP host env. | ./output |
| MAX_MEMORY_MB | No | Soft memory guidance in MB. Default is 1024. | 1024 |
| TEMPLATES_DIR | No | Directory containing templates. Override if you move templates. Default is dist/templates (runtime). | dist/templates |
| DEFAULT_ENGINE | No | LaTeX engine to use: xelatex (default) or pdflatex. Use pdflatex if XeLaTeX isn't installed. | xelatex |
| MAX_LATEX_SIZE | No | Max LaTeX source bytes. Default is 512000. | 512000 |
| COMPILE_TIMEOUT | No | Compile timeout in milliseconds. Default is 60000. | 60000 |
| KEEP_TEMP_ON_FAILURE | No | Set to true to debug failed compiles by keeping temp files. Default is false. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compile_resumeA | Compile LaTeX resume source into a PDF using XeLaTeX (default) or pdfLaTeX. Returns paths and logs. |
| validate_resumeC | Validate LaTeX resume source for structural issues and dangerous constructs before compilation. |
| preview_resumeB | Compile a resume and return preview metadata: page count, PDF size, and compile duration. |
| export_texC | Save LaTeX resume source as a .tex file in the configured output directory. |
| list_templatesA | List all installed resume templates and their variables. |
| compile_templateC | Render a named resume template with JSON variables and compile the result to PDF. |
| versionA | Return server version, supported engines, MCP SDK version, and build information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools are clearly distinct: compilation, validation, preview, export, templates, and version all target different operations. The main confusion is between compile_template and compile_resume—one renders a named template while the other compiles raw LaTeX source, but the distinction (template vs source) is reasonably clear from names.
Tools consistently use a verb_noun pattern throughout (compile_template, compile_resume, preview_resume, export_tex, list_templates, validate_resume). The pattern is mostly regular, though having both compile_template and compile_resume with the same 'compile' verb is a minor deviation from strict one-verb-per-action.
Seven tools is well within the ideal 3-15 range for a resume/pdf generation server. Each tool has a distinct role in the workflow: template management, compilation, validation, preview, export, and metadata.
Core workflows are covered: templates can be listed and compiled, source can be validated, compiled, previewed, and exported. However, there's no obvious update/delete operation for templates, and no tool to manage or inspect output artifacts beyond preview metadata, leaving some minor lifecycle gaps.