MCP server for generating resume PDFs using LaTeX Resume API
MCP server for generating resume PDFs using LaTeX Resume API. Exposed over MCP by the resumake mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
The working resume-tailoring and rendering logic has moved to the tailor-resume skill. The skill runs the original Resumake v2 LaTeX generators locally, supports all nine templates, and does not depend on the discontinued hosted endpoint.
This MCP server acts as a bridge between Claude Desktop and professional resume generation. Simply describe your resume requirements in natural language to Claude, and it will generate a beautifully formatted PDF resume using LaTeX templates. Now with advanced organization features to keep your resumes perfectly organized!
Everything the assistant can do here goes through one of these:
Service — ** latexresu.me - Professional LaTeX resume generation APICredits — ** Thanks to the LaTeX Resume API team for providing the backend service that powers the PDF generationgenerate_resume — Generates a PDF resume from structured data with optional folder organizationcreate_folder — Creates a new folder within the generated-resumes directorylist_folders — Lists all folders and files in the generated-resumes directorycreate_resume_template — The create_resume_template tool exposed by this serverDependencies — The Dependencies tool exposed by this serverContributing — 1. Fork the repository 2. Create a feature branch: git checkout -b feature-name 3. Make your changes and test thoroughly 4. Submit a pull requestBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Resumake MCP's toolset — Service, Credits, generate_resume and 5 more — is a fair guide to whether it matches your workflow. It is maintained by AndreaCadonna; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Service | ** [latexresu.me](https://latexresu.me/) - Professional LaTeX resume generation API |
| Credits | ** Thanks to the LaTeX Resume API team for providing the backend service that powers the PDF generation |
| generate_resume | Generates a PDF resume from structured data with optional folder organization. |
| create_folder | Creates a new folder within the generated-resumes directory. |
| list_folders | Lists all folders and files in the generated-resumes directory. |
| create_resume_template | The create_resume_template tool exposed by this server. |
| Dependencies | The Dependencies tool exposed by this server. |
| Contributing | 1. Fork the repository 2. Create a feature branch: git checkout -b feature-name 3. Make your changes and test thoroughly 4. Submit a pull request with a clear description |
{
"mcpServers": {
"resume-generator": {
"command": "node",
"args": ["path/to/resume-generator-mcp/server.js"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.