toggl-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 |
|---|---|
| nowA | Get a list of existing tags being used in Toggl. Cached daily. |
| get_tagsA | Get a list of existing tags being used in Toggl. Cached daily. |
| get_entry_descriptionsA | Get a list of existing time entry descriptions being used in Toggl. Cached daily. |
| create_time_entryA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| now_resource | Get the current datetime in America/New_York |
| get_tags_resource | Get a list of existing tags being used in Toggl. Cached daily. |
| get_entry_descriptions_resource | Get a list of existing time entry descriptions being used in Toggl. Cached daily. |
TDQS
Scored across 4 tools
The tool 'now' has a description identical to 'get_tags', making them indistinguishable. An agent cannot tell which tool to use without further context, and the purpose of 'now' is unclear.
Most tools follow a verb_noun pattern (get_tags, get_entry_descriptions, create_time_entry), but 'now' breaks the pattern with a vague, single-word name. The mixed conventions make the set feel unpolished.
With only 4 tools, and one being a duplicate, the server feels thin for a Toggl integration. However, the focus on time entry creation and reference data is somewhat coherent, so the count is not egregiously low.
The server supports creating time entries and reading tags/descriptions, but there are no operations to list, update, or delete time entries, nor to manage tags. Significant CRUD operations are missing, which will frustrate agents needing full lifecycle management.