@lewinnovation/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, sent as X-Api-Key on every request. | |
| CLOCKIFY_API_BASE_URL | No | Base URL for the Clockify API. Override only if Clockify documents a different base for your account or region. | https://api.clockify.me/api |
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_current_userA | Returns the currently authenticated Clockify user (from the API key). |
| list_workspacesA | Lists workspaces visible to the authenticated user. For richer role filtering (multiple roles), use clockify_request. |
| list_projectsC | Lists projects in a workspace (supports pagination and filters). |
| list_tasksC | Lists tasks for a project within a workspace. |
| list_time_entriesC | Lists time entries for a user in a workspace. If user_id is omitted, the current API user is used. |
| create_time_entryC | Creates a time entry in a workspace (POST /v1/workspaces/{workspaceId}/time-entries). |
| update_time_entryC | Updates a time entry (PUT /v1/workspaces/{workspaceId}/time-entries/{id}). |
| stop_running_time_entryA | Stops the running timer for a user in a workspace (PATCH .../user/{userId}/time-entries with end time). If user_id is omitted, uses the current API user. |
| clockify_requestB | Low-level access to any documented Clockify v1 endpoint. Path must start with /v1/. Use for endpoints not covered by curated tools. |
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 9 tools
Most tools have distinct purposes based on resource and action. However, 'list_workspaces' and 'get_current_user' are clear, while 'clockify_request' overlaps with all others as a fallback, which could cause some ambiguity. Overall, boundaries are well-defined.
Names mostly follow a consistent verb_noun pattern (list_projects, get_current_user, create_time_entry, etc.), with one outlier: 'clockify_request' breaks the pattern. This minor deviation reduces consistency slightly.
With 9 tools, the set is well-scoped for common Clockify operations like managing projects, tasks, time entries, and workspaces. Each tool appears to earn its place without redundancy.
The surface covers essential CRUD for time entries and listing for other resources. However, there are gaps: no create/update/delete for projects, tasks, or workspaces, though 'clockify_request' provides a workaround. Minor gaps remain for full lifecycle coverage.