Skip to main content
Glama
devpatel25

resumeai-mcp

by devpatel25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to resumeai-mcp

No user-submitted related servers found.

    Related Servers

    • Resume MCP Server

      Adarshcharjan
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes 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.
      1
      MIT

    • ResumePilot MCP

      rajeshaipython-stack
      A
      license
      A
      quality
      B
      maintenance
      Enables parsing a master resume, analyzing job descriptions for ATS/match scores, generating truthful tailored resumes, tracking applications, and producing PDF reports through Claude Desktop.
      17
      MIT

    • jobhunt-copilot

      Frank-Joe-99
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude Desktop or compatible editors to run local, privacy-first job-search workflows including resume generation and STAR polishing, JD matching, GitHub project recommendations, mock interviews, and application tracking. It exposes these capabilities as callable tools through the Model Context Protocol.
      1
      MIT

    • cv-job-assistant

      JahidRayhan
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to parse CVs, search job boards (Remotive, Arbeitnow, Adzuna, Greenhouse/Lever), tailor resumes and cover letters, and prepare application packages with direct apply links—without ever auto-submitting. It runs 100% locally and free, storing jobs and applications as JSON files.
      -

    • ats-scanner-mcp

      jmaitlandsoto
      F
      license
      A
      quality
      C
      maintenance
      Enables local ATS-style resume scanning against job postings, providing match rates, missing keywords, and edit suggestions through Claude Desktop.
      5
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources