A
licenseB
qualityD
maintenanceAutomatically generates and updates CVs/resumes by aggregating data from git commits, Jira tickets, Credly certifications, and existing PDF resumes, with LaTeX formatting support.
14
15
MIT
cvlac-mcp
by stivenson
Related Servers
Alternatives to cvlac-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAutomates LinkedIn profile management, SEO optimization, job search, and content publishing via Playwright.1072 npmMIT
- AlicenseAqualityCmaintenanceExposes a curriculum vitae hosted on a backend REST API to AI assistants over stdio, letting them retrieve the full CV, list and fetch individual sections, and search for terms like technologies or companies. It also provides the full CV as attachable context and a prompt that compares the CV against a job description to suggest improvements.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to tailor a resume to any job description by extracting keywords, analyzing gaps and ATS compliance, managing versions, and compiling PDF/LaTeX outputs entirely locally without external API keys.MIT
- FlicenseNot gradedqualityBmaintenanceEnables creating evidence-based AI proficiency resumes from local AI CLI logs, with privacy-preserving evidence packs and growth tracking.-
- AlicenseAqualityCmaintenanceGenerates professional PDF resumes using LaTeX templates through natural language descriptions. Supports 9 professional templates, AI-powered resume tailoring, and organized folder management for job applications.423MIT
TDQS
A3.8/5.0
Scored across 13 tools
Disambiguation4/5
Most tools target distinct purposes (list read, detail read, profile read, diff, sync, section write), and descriptions draw clear boundaries. Some potential overlap exists between update_section, complete_product, and sync (all write to CvLAC), but the descriptions distinguish their roles adequately.
Naming Consistency4/5
The dominant pattern is verb_noun (read_cvlac, read_portfolio, read_profile, update_section, update_profile, lookup_doi, complete_product, inspect_form). A few single-word verbs (login, sync, diff, screenshot) deviate, but overall it stays predictable and snake_case throughout.
Tool Count5/5
13 tools is well-scoped for a domain covering read/write/sync/lookup/debugging. Each tool earns its place with no obvious filler.
Completeness4/5
The surface covers reading (list, detail, profile), writing (section, profile, post-save completion), diff/sync lifecycle, DOI lookup, and debugging. Deletion is folded into update_section via confirm_delete rather than a dedicated tool, which is a minor but workable gap.