Application Tracker MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APPLICATION_TRACKER_ROOT | Yes | Private local directory for storing application data. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_applicationA | Create a private application record and save its job description locally. |
| list_applicationsA | List private application records, optionally filtered by their status. |
| update_application_statusC | Update one application status and optional private notes. |
| analyse_application_fitA | Compare a private JSON profile to the saved job description without inventing claims. |
| render_application_draftsC | Write editable LaTeX CV/cover-letter starters and a factual tailoring brief locally. |
| create_interview_prepA | Create a private interview-preparation scaffold from factual highlights. |
| compile_application_texB | Compile a generated local .tex artifact with Tectonic; no shell command is used. |
| discover_public_jobsA | Discover listed jobs from a public Greenhouse, Lever, or Ashby API board. This does not log in, bypass restrictions, scrape LinkedIn, or auto-apply. |
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 8 tools
Each tool targets a distinct action and resource: create/list/update applications, analyse fit, render drafts, create interview prep, compile TeX, and discover jobs. There is no overlap or ambiguity between tool purposes.
All tools follow a consistent verb_noun snake_case pattern (create_application, list_applications, update_application_status, analyse_application_fit, etc.). The only minor deviation is the British spelling 'analyse' vs 'analyze', but the pattern is uniform.
Eight tools is well within the ideal 3-15 range and each tool serves a clearly defined function in the application tracking workflow. The count feels appropriate for the domain and not excessive or thin.
The toolset covers the core lifecycle: create, list, update, analyse, render, compile, and prepare for interviews. A delete application tool is missing, and there is no explicit single-application getter, but list_applications can serve that need, so the gaps are minor.