productivity
Clockify CLI for CI
Use the Clockify CLI for CI with headless JSON commands, schema discovery, credentials, and permission controls.
12 functions 8 read 4 write API key auth
Clockify CLI for CI
Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.
Use this shape when a pipeline needs to read or update an external service. The Clockify CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Clockify CLI for CI
kosmokrator integrations:configure clockify --set api_key="$CLOCKIFY_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call clockify.clockify_list_workspaces '{}' --json Discovery Before Execution
Agents and scripts can inspect Clockify docs and schemas before choosing a function.
kosmo integrations:docs clockify --json
kosmo integrations:docs clockify.clockify_list_workspaces --json
kosmo integrations:schema clockify.clockify_list_workspaces --json
kosmo integrations:search "Clockify" --json
kosmo integrations:list --json Useful Clockify CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
clockify.clockify_list_workspaces | Read | none | List all Clockify workspaces the authenticated user belongs to. Returns workspace IDs and names needed for other Clockify tools. |
clockify.clockify_get_workspace | Read | workspace_id | Get details for a single Clockify workspace by ID. |
clockify.clockify_list_projects | Read | workspace_id, name, page, page_size | List projects in a Clockify workspace. Optionally filter by name and paginate results. |
clockify.clockify_get_project | Read | workspace_id, project_id | Get details for a single Clockify project by ID. |
clockify.clockify_create_project | Write | workspace_id, name, color, is_public | Create a new project in a Clockify workspace. |
clockify.clockify_list_time_entries | Read | workspace_id, start, end, project, page, page_size | List time entries in a Clockify workspace. Optionally filter by date range or project. |
clockify.clockify_get_time_entry | Read | workspace_id, time_entry_id | Get details for a single Clockify time entry by ID. |
clockify.clockify_create_time_entry | Write | workspace_id, start, end, description, project_id | Create a new time entry in a Clockify workspace. Provide start/end times, a description, and optionally a project. |
clockify.clockify_update_time_entry | Write | workspace_id, time_entry_id, start, end, description, project_id | Update an existing Clockify time entry. Provide the fields you want to change. |
clockify.clockify_delete_time_entry | Write | workspace_id, time_entry_id | Delete a Clockify time entry. This action cannot be undone. |
clockify.clockify_list_tasks | Read | workspace_id, project_id, page, page_size | List tasks for a Clockify project. |
clockify.clockify_get_current_user | Read | none | Get the authenticated Clockify user profile. Use this to verify your API key is working. |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.