ATimeLogger MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Listen port (default 3000; most hosts inject it) | |
| MCP_PATH | No | Endpoint path (default /mcp) | |
| ATL_TOKEN | Yes | ATimeLogger Personal Access Token the server acts as | |
| ATL_BASE_URL | No | Non-production backend (defaults to https://app.atimelogger.pro) | |
| MCP_AUTH_TOKEN | No | Shared secret required to call /mcp (sent as Authorization: Bearer, x-mcp-token, or query parameter). If unset, the endpoint is open. |
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 |
|---|---|
| list_activity_typesA | List the user's activity types as a tree (groups contain children): names plus internal ids. Use the names when talking to the user; use the ids for exact targeting in other tools. |
| get_current_statusA | Show currently running or paused activities with elapsed time. |
| start_activityA | Start tracking an activity by type name (fuzzy matched, see list_activity_types) or type_id. Optionally backdate the start with |
| stop_activityA | Stop a running or paused activity. type_name may be omitted when exactly one activity is active. Optionally backdate the stop with |
| pause_resume_activityB | Pause a running activity or resume a paused one. |
| log_intervalA | Retroactively log a completed time entry for an activity type. Times are wall-clock in the user's timezone, format "yyyy-MM-dd HH:mm". |
| time_reportA | Aggregated time statistics per activity type for a date range. Returns overall totals plus per-DAY/WEEK/MONTH buckets. |
| list_intervalsA | List raw time entries (intervals) grouped by day for a date range (max 100 days). Paged by day — use |
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 addresses a distinct aspect of time tracking: listing types, checking current status, starting/stopping/pausing activities, logging entries retroactively, and generating reports or raw interval data. There is no overlap between tools; even pause_resume_activity is clearly a single combined operation.
All tool names use snake_case and mostly follow a verb_noun pattern (list_activity_types, start_activity, stop_activity, log_interval, list_intervals). The one exception is time_report, which is noun_noun rather than verb_noun, but it is still clear and fits the overall style.
With 8 tools, the server is well-scoped for its purpose of tracking time. Each tool covers a necessary action without redundancy, and the count sits comfortably in the ideal range for a focused domain.
The tool set covers the full tracking lifecycle: starting, stopping, pausing, resuming, retroactively logging, retrieving current status, viewing raw intervals, and generating aggregated reports. There are no obvious dead ends, as every tracking action has a corresponding read or management tool.