Can I use Toggl Track as a CLI?

Yes. KosmoKrator exposes a Toggl Track CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Toggl Track through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Toggl Track tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Toggl Track credentials stored?

Toggl Track credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Toggl Track MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Toggl Track CLI for Headless Automation

Use the Toggl Track CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write API token auth

Submit Toggl Track feedback View package source

Toggl Track CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Toggl Track CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Toggl Track CLI for Headless Automation
kosmokrator integrations:configure toggl-track --set api_token="$TOGGL_TRACK_API_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call toggl-track.toggl_list_time_entries '{"start_date":"example_start_date","end_date":"example_end_date","workspace_id":1,"project_id":1,"limit":1}' --json

Discovery Before Execution

Agents and scripts can inspect Toggl Track docs and schemas before choosing a function.

kosmo integrations:docs toggl-track --json
kosmo integrations:docs toggl-track.toggl_list_time_entries --json
kosmo integrations:schema toggl-track.toggl_list_time_entries --json
kosmo integrations:search "Toggl Track" --json
kosmo integrations:list --json

Useful Toggl Track CLI Functions

Function	Type	Parameters	Description
`toggl-track.toggl_list_time_entries`	Read	start_date, end_date, workspace_id, project_id, limit	List time entries from Toggl Track. Filter by date range, workspace, or project. Returns recent time entries by default.
`toggl-track.toggl_get_time_entry`	Read	id	Get detailed information about a specific Toggl Track time entry by its ID.
`toggl-track.toggl_create_time_entry`	Write	workspace_id, description, duration, start, pid, tags, billable, created_with	Create a new time entry in Toggl Track. Provide a description, workspace, start time, and duration. Optionally assign to a project, add tags, or mark as billable.
`toggl-track.toggl_list_projects`	Read	active, workspace_id	List projects from Toggl Track. Optionally filter by workspace or active status.
`toggl-track.toggl_get_project`	Read	id	Get detailed information about a specific Toggl Track project by its ID.
`toggl-track.toggl_list_workspaces`	Read	none	List all Toggl Track workspaces accessible to the authenticated user. Returns workspace IDs and names needed for other operations.
`toggl-track.toggl_get_current_user`	Read	none	Get the authenticated Toggl Track user profile, including email, name, default workspace, and time zone.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Toggl Track CLI Pages

CI Toggl Track CLI for CI. Cron Jobs Toggl Track CLI for cron jobs. Shell Scripts Toggl Track CLI for shell scripts. Coding Agents Toggl Track CLI for coding agents.