work-tracker-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORK_TRACKER_DIR | No | Override the default folder ~/Desktop/work-tracker/ | ~/Desktop/work-tracker/ |
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 |
|---|---|
| get_current_workA | Get today's work log: current focus, project path, and progress entries. Call at the start of sessions to resume context. |
| set_focusA | Set or update what the user is currently working on today. Use when starting a new task or shifting focus. |
| log_progressA | Append a timestamped note to today's work log. Use after completing a step, making a decision, or hitting a blocker. |
| read_dayB | Read the work log for a specific day. |
| list_daysA | List available work log days, newest first. |
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 5 tools
Each tool has a distinct purpose: get_current_work for today's summary, set_focus for updating focus, log_progress for appending entries, read_day for specific days, and list_days for enumeration. No overlap or ambiguity in their roles.
All tool names follow a clear verb_noun pattern in snake_case (get_current_work, set_focus, log_progress, read_day, list_days). The verbs vary to match the actions, but the convention is consistent across the set.
With 5 tools, the server is well-scoped for a daily work tracker. Each tool covers a core operation without redundancy, making the count feel appropriate and manageable.
The set covers the essential lifecycle of daily work tracking: get current context, set focus, log progress, read historical days, and list available days. Minor gaps exist (e.g., no edit/delete for log entries), but they are not critical for the server's purpose.