Time Tracking MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMPANIES | No | Comma-separated list of companies | default |
| DEFAULT_COMPANY | No | Default company when not specified (default: first company) | |
| TIME_TRACKING_DIR | No | Where to store markdown files | ~/Documents/time-tracking |
| DISPLAY_TIMEZONE_OFFSET | No | Hours offset from UTC | 0 |
| DISPLAY_TIMEZONE_STRING | No | Timezone display name | UTC |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| log_timeA | Log a completed time entry. This tool records work you've done. Natural language examples Claude should parse:
Claude should extract:
|
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'log_time' has a clear, distinct purpose of recording time entries, so agents cannot misselect between non-existent alternatives.
The naming pattern cannot be inconsistent with only one tool. The tool name 'log_time' follows a clear verb_noun convention that would be appropriate if more tools were added, but with a single tool, consistency is inherently perfect.
A single tool is insufficient for a time tracking domain that typically requires operations like listing, editing, deleting, or reporting on time entries. While the tool itself is well-described, the server's scope feels incomplete with only creation/logging functionality, lacking basic CRUD coverage.
The tool set is severely incomplete for time tracking. There is no way to retrieve, update, delete, or analyze logged time entries—only creation via 'log_time'. This creates dead ends for agents that need to review or modify existing data, significantly limiting practical utility.