Lazy Toggl MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOGGL_API_TOKEN | Yes | Your Toggl API token for authentication |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_trackingB | Start tracking time for a new task |
| stop_trackingA | Stop the currently running time entry |
| list_workspacesA | List all available workspaces |
| show_current_time_entryA | Show the currently running time entry, if any |
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 targets a distinct action: starting, stopping, listing workspaces, and viewing the current entry. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (start_tracking, stop_tracking, list_workspaces, show_current_time_entry).
Four tools is well-scoped for a minimal time tracking server, covering the essential actions without unnecessary bloat.
The core start/stop/current workflow is covered, but there are significant gaps: no way to view past time entries, update, or delete them. After stopping, users have no way to review what was tracked.