resumeai-mcp
Related Servers
Alternatives to resumeai-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceExposes a structured professional resume as a set of AI-queryable tools, enabling AI clients like Claude Desktop to query summary, experience, skills, projects, and tailor resumes to job descriptions.1MIT
- AlicenseAqualityBmaintenanceLets AI agents create and drive Claude Code cloud sessions natively over stdio, exposing typed tools to start a session from a task description, queue follow-up messages into an existing session, and check the CLI's sign-in state. Each tool maps to a fixed Claude Code CLI invocation with strict schemas and structured JSON results, so agents never write shell commands or run local sessions.7542 npmMIT
- AlicenseAqualityCmaintenanceEnables an AI agent to run local tools on the user's own machine via stdio, including command execution, workspace file read/write, and system status checks.52MIT
- 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
- AlicenseAqualityBmaintenanceEnables Claude Code and OpenAI Codex CLI to act as bidirectional partners by letting each ask the other for code review, explanations, planning, performance analysis, and implementation help. It also provides background job tools for starting, observing, waiting on, and cancelling delegated tasks.6373 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables an AI client to manage candidate profiles and job postings stored in a local PostgreSQL database, match them deterministically, and generate tailored resume and cover-letter PDFs in English, French, German, and generic formats. It runs over stdio or a loopback HTTP endpoint with a bearer token, exposing 34 tools by default plus opt-in tools for imports, link fetching, deletions, and document export.1MIT
TDQS
Scored across 6 tools
Each tool maps to a distinct step in the scan lifecycle: auth_status (auth check), list_scans (history), start_scan (create), get_scan_status (poll), get_scan_feedback (results), delete_scan (remove). The boundaries between polling status, retrieving feedback, and starting a scan are clear and non-overlapping.
Most tools follow a clean verb_noun pattern (list_scans, start_scan, get_scan_status, get_scan_feedback, delete_scan). auth_status deviates slightly by leading with a noun-like token rather than an explicit verb, but it remains readable and consistent with the scan-status naming family.
Six tools is well-scoped for a scan-and-feedback workflow, with each tool earning its place across auth, listing, creation, polling, results, and deletion. Nothing feels padded or redundant.
The surface covers the full lifecycle: authentication, listing, starting, polling, fetching feedback, and deletion. Minor gaps exist (no explicit cancel/abort for an in-flight scan or resume-management operation), but these are workable given the one-scan-in-flight constraint and idempotent start.