job-application-tracker-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOB_TRACKER_FILE | No | Path to the JSON file where applications are saved. Defaults to ~/.job-application-tracker-mcp/applications.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_applicationA | Add a job or internship to the tracker. It starts in the applied stage unless you pass another status. Inputs: company and role (both required), an optional deadline as YYYY-MM-DD, an optional source such as LinkedIn or a career fair, an optional type of job or internship, an optional status and optional notes. The tool saves the application on this computer and returns its id, which update_status needs. Example prompt: "Add a Software Intern role at Shopify with a deadline of 2026-11-15, found on LinkedIn." |
| update_statusA | Move an application to another stage: applied, interview, offer or rejected. Inputs: id of the application (from add_application or export_report), the new status, an optional interview_date as YYYY-MM-DD or YYYY-MM-DDTHH:MM, and an optional note that is added to the notes. When the status is interview, pass interview_date so list_upcoming can remind you. Example prompt: "Move application 1 to interview on 2026-11-20 at 14:30." |
| list_upcomingA | Show upcoming deadlines and interviews sorted by date, with a reminder for each one. Deadlines come from applications still in the applied stage, and interviews come from applications in the interview stage that have an interview_date. Rejected applications and offers are left out. Inputs: optional days, how far ahead to look (default 14), include_overdue (default true) to also show deadlines that already passed, and an optional today as YYYY-MM-DD to ask as if it were another day. Example prompt: "What deadlines and interviews do I have in the next two weeks?" |
| export_reportA | Export your applications as CSV or Markdown so you can share them or open them in a spreadsheet. Inputs: format, either csv or markdown (default markdown), and an optional status to export only that stage. The report is returned as text and nothing is written to disk. In CSV, a cell that starts with =, +, - or @ gets a leading apostrophe so spreadsheets do not run it as a formula. Example prompt: "Export all my applications as a CSV." |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool maps to a distinct action on the application lifecycle: create, change stage, view upcoming dates, and export. There is no plausible confusion between update_status and add_application since one requires an id and only mutates the stage. list_upcoming and export_report both read data but differ clearly in output shape and purpose.
All four tools follow a clean verb_noun snake_case pattern (add_application, update_status, list_upcoming, export_report). Verbs are distinct and predictable in meaning. No style mixing or vague naming.
Four tools is on the thin side but each earns its place in a small tracker workflow. The surface is intentionally minimal rather than padded with redundant operations. A slightly richer set (e.g. a get/list-all tool) would round it out without bloat.
Core create/update/view/export flows exist, but there is no way to list or fetch all applications directly, no delete/archive operation, and no way to edit company, role, deadline, or source after creation (only the stage and notes). Agents must use export_report as a workaround to see the full list, and cannot correct mistakes.