clockify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOCKIFY_API_KEY | Yes | Your Clockify API key, obtained from Preferences → Advanced → API. | |
| CLOCKIFY_WORKSPACE_ID | No | Optional workspace ID. If not set, the server uses your active workspace from the user endpoint. |
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_projectsA | List projects in the Clockify workspace. Use this to find the projectId needed by start_timer and log_time. Active projects only unless includeArchived is set. |
| list_tasksA | List active tasks belonging to a Clockify project. Use this to find the taskId for start_timer and log_time. Requires a projectId from list_projects. |
| list_tagsA | List tags in the workspace, for the tagIds argument of start_timer / log_time. |
| current_timerA | Show the currently running Clockify timer, with elapsed time so far. Returns a plain message when nothing is running. |
| start_timerA | Start a running Clockify timer. Clockify allows only one running timer at a time, so this stops any timer already running. Use list_projects / list_tasks first if you need ids. |
| stop_timerA | Stop the currently running Clockify timer and report the logged duration. Reports plainly when no timer was running. |
| log_timeA | Create a completed Clockify time entry for a past interval. Use this to back-fill work you did not time live. Does not touch the running timer. |
| list_time_entriesA | List your Clockify time entries for a period, with a total. Defaults to today. Times are shown in local time. |
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 targets a distinct resource or action: live timer controls, historical entry listing/creation, and reference lookups. start_timer and log_time are clearly separated by live vs. past work, and current_timer is clearly distinct from list_time_entries.
Seven of eight tools follow a consistent verb_noun pattern (start_timer, stop_timer, log_time, list_*). current_timer is the only outlier, using a noun phrase instead of a verb-led name.
Eight tools is well-scoped for a focused Clockify time-tracking server. Each tool earns its place: timer state, entry creation/listing, and ID lookups for projects, tasks, and tags.
The core timer loop and time listing are well covered, but updating or deleting time entries is missing. An agent cannot correct or remove a mistakenly logged entry, which is a notable workflow dead end.