Skip to main content
Glama
Sign In
job-hunt-mcp-server

job-hunt-mcp-server

by OpenCode-Projects-AtlasRearden8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to job-hunt-mcp-server

No user-submitted related servers found.

    Related Servers

    • mcp-job-tracker

      developermaroof
      A
      license
      B
      quality
      C
      maintenance
      Enables Claude to record job applications in a local JSON file and then list them, change their status (applied, replied, interview, rejected, offer), and surface stale applications that need a follow-up. Requires no database or account, and validates every input so saves stay clean.
      4
      1
      MIT

    • zhiro

      mazjq
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to research industries and companies, track job postings and deadlines from recruiting sites and spreadsheets, match roles against a personal profile, manage application stages, and fill in application forms up to but not including submission. All data stays in a local folder on the user's machine, with reversible actions and confirmation cards for consequential steps.
      1
      MIT

    • Dossier

      victorcheeney
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI agent to maintain a job-search profile and applications, read public job-board forms, draft answers and tailored résumés, track stages and notes, and keep local web pages updated live.
      17 npm
      MIT

    • career-ops-mcp

      Aryanpawar67
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables tracking of job applications and freelance leads through an MCP interface, with tools to add and update items, list and summarize the pipeline, flag stale entries, and draft follow-up messages grounded in each item's logged notes using locally stored JSON data.
      MIT
    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

    B3.2/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target a clear resource+action, and the three query tools (list_applications, what_is_due_this_week, find_stale_applications) have distinct intents. The main overlap is update_application accepting a `status` field while set_status also exists with automatic contact-date side effects, which could lead an agent to pick the wrong one and silently skip that logic.

    Naming Consistency4/5

    The dominant pattern is verb_noun (add_application, update_application, add_contact, add_interview_feedback, find_stale_applications, draft_follow_up). Minor deviations: set_status omits the domain noun used elsewhere, and what_is_due_this_week breaks the pattern with a question-phrase style, but overall it stays readable and predictable.

    Tool Count5/5

    Nine tools is well-scoped for a personal job-application tracker: core CRUD, contact logging, and three targeted views/actions. Each tool covers a distinct workflow step without padding.

    Completeness3/5

    Creation, update, listing, and due/stale views are covered, but there is no delete/archive for applications or contacts and no way to read back stored interview feedback once recorded. Agents can work around some gaps via status changes but cannot remove or retrieve certain records.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources