Skip to main content
Glama
Job Tracker MCP Server

Job Tracker MCP Server

by AshC2004

Job Tracker MCP Server

A Model Context Protocol (MCP) server for tracking job applications and follow-ups, built with FastMCP and SQLite. Lets Claude Desktop, Cursor, or any MCP client log applications, move them through the hiring pipeline, schedule follow-up reminders, and check the health of an active job search through natural conversation.

Features

  • Log job applications with company, role, applied date, status, job URL, and notes

  • Move applications through a fixed set of pipeline stages, with validation on transitions

  • List applications, optionally filtered by status, most recent first

  • Schedule follow-up reminders tied to a specific application

  • Query pending follow-ups due on or before a given date, so you can ask "what follow-ups do I have this week"

  • Mark follow-ups as done

  • Get a pipeline summary: counts of applications grouped by status

  • The valid pipeline stages exposed as an MCP resource for client discovery

Related MCP server: JobTrack MCP Server

Tools

Tool

Description

add_application(company, role, date_applied, status, job_url, notes)

Insert a new job application

update_status(application_id, new_status)

Move an application to a new pipeline status

list_applications(status)

List applications, optionally filtered by status, newest first

add_followup(application_id, follow_up_date, note)

Schedule a follow-up reminder for an application

get_pending_followups(as_of_date)

List follow-ups due on or before a date that are not yet done

mark_followup_done(followup_id)

Mark a follow-up as completed

pipeline_summary()

Count applications grouped by pipeline status

All dates use YYYY-MM-DD format and are validated on input. Valid pipeline stages are: applied, phone_screen, technical_interview, onsite, offer, rejected, withdrawn. Passing any other value to status or new_status raises a clear error.

Resources

  • pipeline://stages: JSON array of the ordered pipeline stages, so a client can discover valid status values without guessing.

Setup

Requires Python 3.11+ and uv.

uv sync

Claude Desktop config

{
  "mcpServers": {
    "job-tracker": {
      "command": "/path/to/job-tracker-mcp-server/run.sh"
    }
  }
}

Replace /path/to/job-tracker-mcp-server with the absolute path to this repo.

Storage

Data is stored in a local SQLite database (applications.db, created automatically on first run, gitignored). Override the location with the JOB_TRACKER_DB_PATH environment variable.

Testing

uv run pytest

License

MIT

Available Tools

7 tools
add_applicationB

Add a new job application to the tracker.

Inputs: role (required), company (required), date_applied (required), notes, +2 more. Returns: object

add_followupB

Schedule a follow-up reminder tied to an application.

Inputs: application_id (required), follow_up_date (required), note. Returns: object

get_pending_followupsA

List follow-ups due on or before the given date that are not done.

Inputs: as_of_date (required). Returns: Generic wrapper for non-object return types.

list_applicationsA

List job applications, optionally filtered by status, newest first.

Inputs: status. Returns: Generic wrapper for non-object return types.

mark_followup_doneB

Mark a follow-up reminder as completed.

Inputs: followup_id (required). Returns: object

pipeline_summaryA

Return counts of applications grouped by pipeline status.

Inputs: no named parameters. Returns: Generic wrapper for non-object return types.

update_statusB

Update the pipeline status of an existing application.

Inputs: new_status (required), application_id (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: application creation/status/list, follow-up creation/listing/completion, and pipeline summary. There is no overlap between the application and follow-up subdomains.

    Naming Consistency5/5

    All tool names follow a clear verb_noun pattern with snake_case (e.g., add_application, list_applications, mark_followup_done). The consistency makes the toolset predictable and easy to navigate.

    Tool Count5/5

    Seven tools is a well-scoped count for a job tracker. Each tool covers an essential operation, and the number feels neither excessive nor sparse for the domain.

    Completeness4/5

    The toolset covers the core lifecycle: adding applications, updating status, listing with filters, and follow-up management. It lacks a delete application or update application details, but these are minor gaps that can be worked around.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables users to manage job applications (add, list, update status) through natural language conversations, using Notion as the backend.
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Manages job applications, companies, roles, statuses, deadlines, and reminders through natural language queries.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables job-search application tracking through a private application board, managing application facts, stage history, and interview prep documents while leaving summarization and decision-making to the connected agent.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage a personal job application tracker, allowing users to list, add, update, and delete job applications with company, role, and status details through natural language.
      -