Model Context Protocol-Server, der einen Lebenslauf anhand von 5 echten ATS-Parsern prüft.
Stellt drei MCP-Tools bereit, damit jeder MCP-kompatible KI-Agent (Claude Code, Cursor, Windsurf, Zed, OpenCode, Cline usw.) einen Lebenslauf anhand der dokumentierten Eigenheiten folgender Systeme analysieren kann:
Workday
Greenhouse
Lever
Taleo (Oracle)
iCIMS
Dies sind die 5 am häufigsten verwendeten Enterprise-ATS-Systeme. Jedes davon parst Lebensläufe leicht unterschiedlich. Ein "0–100 ATS-Score" mittelt diese Unterschiede zu Rauschen. Dieser Server zeigt auf, was jedes System tatsächlich tut – Spaltenbehandlung, Entfernen von Emojis, Ignorieren von Kopf- und Fußzeilen, Eigenheiten bei Datumsformaten – als konkrete Lint-Ergebnisse mit konkreten Korrekturvorschlägen.
Die Lint-Regeln basieren auf öffentlichen Herstellerdokumentationen. Siehe docs/vendor-sources.md für Quellenangaben.
Related MCP server: decroche-mcp
Tool | Beschreibung |
| Vollständiger Bericht. Nimmt einen Dateipfad zum Lebenslauf (PDF oder DOCX) entgegen und gibt herstellerspezifische Lint-Ergebnisse mit Schweregrad ( |
| Lint für einen einzelnen Hersteller. Nimmt einen Pfad + Herstellernamen entgegen. Schneller, wenn der Benutzer nur an einem bestimmten ATS interessiert ist. |
| Gibt die URL der visuellen Web-Begleitanwendung (cv-mirror-web.vercel.app) für Benutzer zurück, die eine Side-by-Side-Parser-Ansicht im Browser einer Agenten-Sitzung vorziehen. |
npm install -g cv-mirror-mcpFügen Sie dies zur Konfigurationsdatei Ihres MCP-Clients hinzu:
Claude Code (~/.claude/mcp.json oder .claude.json im Projekt):
{
"mcpServers": {
"cv-mirror": {
"command": "npx",
"args": ["-y", "cv-mirror-mcp"]
}
}
}Cursor / Windsurf / Zed / Cline: gleiches Konfigurationsformat (einfügen, wo immer Ihr Client mcpServers liest).
Starten Sie den Client neu. Die drei oben genannten Tools werden automatisch registriert.
Nach der Installation fragen Sie einfach Ihren Agenten:
Scan my CV at
~/Documents/resume.pdfand tell me what each ATS would do to it.
Der Agent ruft analyze_cv auf, die Lint-Engine läuft lokal (kein Netzwerk, kein Upload), und der Agent zeigt die strukturierte Ausgabe an:
CV Mirror — multi-vendor ATS lint report
Source: /Users/jane/Documents/resume.pdf
Format: pdf
Pages: 2
Words: 542
[ERROR] Workday
- ERROR WORKDAY_MULTI_COLUMN: 35% of lines look multi-column. Workday's parser
reads left-to-right and interleaves both columns into one stream.
Fix: Convert to single-column layout. Move sidebars (Skills, Tools, Languages)
above or below the main content.
[OK] Greenhouse
No issues detected by the simulated parser.
[WARN] Lever
- WARN LEVER_HEADER_FOOTER: Header/footer-like text detected ("Page 1 of 2").
Lever historically drops content placed in PDF headers/footers.
Fix: Remove headers and footers. Page numbers are not needed on a CV.
...Dies sind echte Heuristiken, die aus öffentlichen ATS-Dokumenten und Support-Artikeln der Hersteller abgeleitet wurden. Die vollständige Liste mit Quellenangaben befindet sich in docs/vendor-sources.md.
Regel | Hersteller | Schweregrad | Auslöser |
| Workday | error | >15% der Zeilen haben eine Lücke von 5+ Leerzeichen |
| Workday | warn | Datumsangaben verwenden das Format "Q3 2024" |
| Workday | error | Keine E-Mail oder Telefonnummer im Klartext |
| Greenhouse | warn | Beliebiger Emoji-Codepoint erkannt |
| Greenhouse | info | Nicht-standardisierte Aufzählungszeichen |
| Greenhouse | warn | "My Story", "Highlights Reel" usw. |
| Lever | warn | "Seite X von Y"-Muster erkannt |
| Lever | error | Keine "Experience"/"Education"-Abschnitte |
| Taleo | warn | ISO-Datumsangaben überwiegen Monat-Jahr-Datumsangaben |
| Taleo | error | <1 Wort pro kB Dateigröße |
| Taleo | info | Geschwungene Anführungszeichen erkannt |
| iCIMS | error | >20% der Zeilen mehrspaltig |
| iCIMS | warn | <2 Standard-Überschriften gefunden |
Node.js >= 18
Ein MCP-kompatibler Client (Claude Code, Cursor, Windsurf, Zed, Cline usw.)
Der Server läuft lokal innerhalb des Prozesses Ihres Agenten. Kein Upload-Endpunkt. Keine Telemetrie. Ihre Lebenslauf-Daten verlassen niemals Ihren Rechner.
Die visuelle Web-Begleitanwendung unter cv-mirror-web.vercel.app ist ebenfalls vollständig clientseitig – dieselbe Engine, läuft im Browser.
git clone https://github.com/goofypluto999/cv-mirror-mcp.git
cd cv-mirror-mcp
npm install
npm test19 Unit-Tests, die Signalerfassung und das Auslösen von Regeln pro Hersteller abdecken.
CV Mirror (web) — visuelle Side-by-Side-Parser-Ansicht. Dieselbe Lint-Engine. Ziehen Sie ein PDF per Drag-and-Drop hinein und sehen Sie das Overlay der Lesereihenfolge auf dem tatsächlichen Dokument.
Vantage AI — sobald Ihr Lebenslauf die Parser passiert hat, ist das nächste Problem die Bewerbung: maßgeschneidertes Anschreiben, simuliertes Vorstellungsgespräch, Eignungsanalyse. Vantage übernimmt diesen Ablauf. Kostenpflichtig (£5 Starter / 20 Token, 10 kostenlose Token bei der Anmeldung).
Pull Requests sind willkommen. Besonders interessiert an:
Weitere Herstellersimulatoren (BambooHR, SmartRecruiters, JazzHR, Recruitee usw.)
Aktualisierte Regeln, wenn Hersteller ihr Parsing-Verhalten ändern (öffnen Sie ein Issue mit dem Quellenlink)
Übersetzungen der Lint-Ausgabe
MIT. Workday, Greenhouse, Lever, Taleo und iCIMS sind Marken ihrer jeweiligen Eigentümer. Dieses Projekt ist mit keinem von ihnen verbunden; die Namen werden zur beschreibenden Referenz verwendet (nominative fair use).
Erstellt von Vantage Labs.
Analyse a CV (PDF or DOCX) against 5 real ATS parsers (Workday, Greenhouse, Lever, Taleo, iCIMS). Returns per-vendor lint findings, parse risk score, and concrete fixes. Use when the user asks 'is my CV ATS-friendly', 'will my resume pass [vendor]', or 'why am I not getting interviews' (with a file path).
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Absolute path to the CV file (PDF or DOCX). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so description carries full burden. It discloses tool reads PDF/DOCX, runs against 5 parsers, and returns findings. Does not mention file size limits, processing duration, or if file is uploaded elsewhere, but is largely transparent about its operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two focused sentences: first defines action and output, second provides usage examples. No unnecessary words. Excellent front-loading of purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, description explains return types (per-vendor lint findings, risk score, fixes). Mentions supported file types. Could add error handling details (e.g., missing file), but otherwise complete for a single-parameter tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 100% coverage with description for the single 'path' parameter. The description does not add further details beyond schema, but schema itself is sufficient. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool analyzes CVs against 5 ATS parsers, returning per-vendor lint findings, risk score, and fixes. It clearly distinguishes from siblings by covering multiple vendors (vs. lint_for_vendor which likely targets one).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description provides explicit user query triggers ('is my CV ATS-friendly', 'will my resume pass [vendor]', 'why am I not getting interviews') and mentions file path requirement. Lacks explicit when-not-to-use or mention of sibling alternatives, but context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns the URL for the visual web companion tool (CV Mirror) where the user can drag-drop a CV and see the side-by-side parser view in their browser. Useful when the user wants the visual reading-order overlay or doesn't want to share a file path.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. States it returns a URL, implying read-only, but does not explicitly declare non-destructive behavior or other constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no unnecessary words, front-loaded with purpose. Highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a zero-parameter, no-output-schema tool. Explains function and usage context. Minor gap: doesn't explicitly state no input needed, but schema implies it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters (schema coverage 100%), baseline 4. Description adds meaning by explaining the purpose of the URL beyond the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clear verb+resource: 'Returns the URL' for a specific visual tool (CV Mirror). Distinguishes from siblings (analyze_cv, lint_for_vendor) by offering a different capability.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
States when it's useful (visual reading-order overlay, avoiding file path sharing). Does not explicitly exclude alternative uses but context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Run lint for ONE specific ATS vendor only. Use when the user asks something vendor-specific like 'will my CV pass Workday' or 'what would Greenhouse strip from this'. Vendor must be one of: workday, greenhouse, lever, taleo, icims.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Absolute path to the CV file (PDF or DOCX). | |
| vendor | Yes | ATS vendor to simulate. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It does not explain whether the tool is read-only, what side effects exist, or what the output format is. The term 'lint' implies analysis but lacks detail.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core action and constraint. Each sentence adds value: one states the purpose and allowed vendors, the other gives usage examples. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite its simplicity, the tool has no output schema and the description does not explain what the lint result looks like (e.g., a score, a list of issues). The user cannot infer the return format without additional context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 100% coverage with clear descriptions. The description adds context for the vendor enum by specifying use cases, but adds no extra meaning for the path parameter beyond its schema description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states 'Run lint for ONE specific ATS vendor only', with a clear verb and resource. It lists the allowed vendors and uses examples to distinguish from siblings like analyze_cv, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly provides when-to-use examples ('when the user asks something vendor-specific like...'). Does not explicitly state when not to use or name an alternative tool, though the sibling names imply a general CV analysis tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0analyze_cvget_express_urllint_for_vendorScored across 3 tools
The tools have distinct purposes: analyze_cv for all vendors, lint_for_vendor for a single vendor, and get_express_url for a visual URL. However, analyze_cv and lint_for_vendor both analyze CVs, which could cause minor confusion if descriptions are not read carefully.
Tool names follow a verb_noun pattern but with inconsistency: 'analyze_cv' and 'get_express_url' are direct, while 'lint_for_vendor' uses a preposition. The verb 'lint' is less standard than 'analyze'.
With 3 tools, the set is small but well-scoped for the domain of CV ATS analysis. It covers the essential operations without being overly sparse.
The tool set covers comprehensive analysis, vendor-specific linting, and a visual companion tool. Minor gaps like listing vendors or handling multiple files are absent but not critical for the core functionality.
Generate tailored, ATS-optimized resume PDFs and cover letters from a job description, over MCP.
Public MCP server for discovering open jobs. Search, filter, and get application links.
Document-to-Markdown MCP server — convert PDF, Office and HTML into LLM-ready Markdown.
Document conversion MCP server: PDF to Markdown, image OCR, spreadsheet parsing.
