MCP Toggl Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOGGL_API_KEY | Yes | Your Toggl API key (get from https://track.toggl.com/profile) | |
| TOGGL_CACHE_TTL | No | Cache TTL in milliseconds (default: 1 hour) | 3600000 |
| TOGGL_CACHE_SIZE | No | Maximum number of cached entities (default: 1000) | 1000 |
| TOGGL_DEFAULT_WORKSPACE_ID | No | Your default workspace ID |
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 |
|---|---|
| toggl_check_authB | Verify Toggl API connectivity and authentication is valid |
| toggl_get_time_entriesB | Get time entries with optional date range filters. Returns hydrated entries with project/workspace names. |
| toggl_get_current_entryB | Get the currently running time entry, if any |
| toggl_start_timerC | Start a new time entry timer |
| toggl_stop_timerB | Stop the currently running timer |
| toggl_daily_reportB | Generate a daily report with hours by project and workspace |
| toggl_weekly_reportC | Generate a weekly report with daily breakdown and project summaries |
| toggl_project_summaryC | Get total hours per project for a date range |
| toggl_workspace_summaryB | Get total hours per workspace for a date range |
| toggl_list_workspacesB | List all available workspaces |
| toggl_list_projectsC | List projects for a workspace |
| toggl_list_clientsC | List clients for a workspace |
| toggl_warm_cacheC | Pre-fetch and cache workspace, project, and client data for better performance |
| toggl_cache_statsB | Get cache statistics and performance metrics |
| toggl_clear_cacheB | Clear all cached data |
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 15 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools like toggl_start_timer and toggl_stop_timer handle timer control, while toggl_get_time_entries and toggl_get_current_entry focus on retrieving time data, and reporting tools like toggl_daily_report and toggl_weekly_report serve specific output formats. There is no overlap in functionality.
All tools follow a consistent verb_noun pattern with the 'toggl_' prefix, using snake_case throughout. Examples include toggl_list_workspaces, toggl_start_timer, and toggl_clear_cache, making the naming predictable and easy to understand.
With 15 tools, the count is well-scoped for a Toggl time-tracking server. It covers authentication, data listing, timer operations, reporting, and caching without being overwhelming, with each tool earning its place in the workflow.
The tool set provides strong coverage for core time-tracking operations, including CRUD-like actions (list, start/stop, get entries) and reporting. A minor gap is the lack of tools for updating or deleting time entries, which agents might need to work around, but overall, the surface is nearly complete for the domain.