time-tracker-ai-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| start_timerB | Start a time tracking timer for a project. Optionally add a task description and comma-separated tags. |
| stop_timerB | Stop the running timer and log the time entry. Optionally add notes. |
| get_reportA | Generate a time report. Optionally filter by project. Shows totals per project and per day. |
| list_entriesB | List recent time entries. Optionally filter by project. Returns up to limit entries (default 20). |
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 has a distinct purpose: starting/stopping timers, listing entries, and generating reports. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (get_report, list_entries, start_timer, stop_timer).
4 tools cover the essential time tracking workflow without redundancy. The count is well-scoped for the domain.
Covers all core operations (start, stop, list, report). Minor gaps like manual entry editing or deletion are absent but acceptable for a timer-focused tool.