clockify-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOCKIFY_API_KEY | Yes | Your Clockify API key (found in Profile Settings → API) | |
| CLOCKIFY_WORKSPACE_ID | No | Override workspace ID. If omitted, the first workspace is used automatically. |
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 |
|---|---|
| get_workspacesB | List all Clockify workspaces |
| get_current_userB | Get the authenticated Clockify user info |
| get_projectsC | List projects in the workspace |
| get_clientsC | List clients in the workspace |
| get_tagsC | List tags in the workspace |
| get_time_entriesC | List time entries for the current user |
| get_current_timerA | Get the currently running timer (null if no timer is running) |
| create_time_entryB | Create a time entry. Omit |
| stop_timerC | Stop the currently running timer |
| update_time_entryC | Update (full replace) an existing time entry by ID |
| delete_time_entryC | Delete a time entry by ID |
| submit_for_approvalC | Submit time entries for manager approval for a given week/period |
| get_tasksC | List tasks within a project |
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 13 tools
Each tool targets a distinct resource or action: retrieval of workspaces/users/projects/clients/tags/tasks, CRUD for time entries, and timer control. The only potential overlap is between get_current_timer and get_time_entries, but descriptions clearly differentiate them.
All tool names use snake_case with a consistent verb_noun pattern (get_, create_, update_, delete_, stop_, submit_). No deviations or mixed conventions.
13 tools is well within the typical 3-15 range for a focused MCP server. Each tool corresponds to a meaningful operation in the Clockify domain, with no obvious redundancies.
The server covers the full lifecycle for time entries (create, read, update, delete, start/stop timer, submit for approval) and provides read access to supporting entities. However, it lacks create/update/delete operations for projects, clients, tags, and tasks, which may limit management workflows.