Toggl Track MCP integration for AI agents.
Connect AI agents to Toggl Track through 24 structured actions, including get current time entry, create project, delete project, and stop time entry. Review…
- ACTION CONTRACTS
- 24
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Toggl Track integration exposes
The Toggl Track Agent App exposes 24 provider-backed actions for productivity work. Its current contract lets an authorized agent get the currently running toggl track time entry, if any, create a toggl track project, and delete a toggl track project. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Toggl Track account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Toggl Track capabilities.
Showing 12 of 24 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_time_entryREADGet the currently running Toggl Track time entry, if any.
create_projectWRITECreate a Toggl Track project.
INPUTS: workspaceId / name / active / billable / clientId
delete_projectHIGH IMPACTDelete a Toggl Track project.
INPUTS: workspaceId / projectId
stop_time_entryREVIEWStop a running Toggl Track time entry.
INPUTS: workspaceId / timeEntryId
create_tagWRITECreate a Toggl Track tag.
INPUTS: workspaceId / name
create_taskWRITECreate a Toggl Track task.
INPUTS: workspaceId / projectId / name / active / estimatedSeconds
create_time_entryWRITECreate a Toggl Track time entry.
INPUTS: workspaceId / billable / createdWith / description / duration
delete_tagHIGH IMPACTDelete a Toggl Track tag.
INPUTS: workspaceId / tagId
delete_taskHIGH IMPACTDelete a Toggl Track task.
INPUTS: workspaceId / projectId / taskId
delete_time_entryHIGH IMPACTDelete a Toggl Track time entry.
INPUTS: workspaceId / timeEntryId
get_current_userREADGet the current Toggl Track user profile.
get_projectREADGet one Toggl Track project.
INPUTS: workspaceId / projectId
INPUT CONTRACTS
Know what the action needs before it runs.
create_project
workspaceIdREQUIRED- The Toggl Track workspace ID.
nameOPTIONAL- The project name.
activeOPTIONAL- Whether the project should be active.
billableOPTIONAL- Whether the project should be billable.
clientIdOPTIONAL- The client ID to associate with the project.
delete_project
workspaceIdOPTIONAL- The Toggl Track workspace ID.
projectIdOPTIONAL- The Toggl Track project ID.
stop_time_entry
workspaceIdOPTIONAL- The Toggl Track workspace ID.
timeEntryIdOPTIONAL- The Toggl Track time entry ID.
create_tag
workspaceIdOPTIONAL- The Toggl Track workspace ID.
nameOPTIONAL- The tag name.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current Time Entry
Get the currently running Toggl Track time entry, if any. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_time_entryControl Create Project
Create a Toggl Track project. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_projectVerify with Create Project
Create a Toggl Track project. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_projectSAFETY BOUNDARY
Operate Toggl Track with explicit limits
- Authorize Toggl Track with API key and grant only the provider access required by the selected actions.
- 12 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_project`, `delete_tag`, and `delete_task` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Toggl Track rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Toggl Track task completed successfully.
CONNECTION MODEL
API key
Toggl Track API token. It is sent with HTTP Basic auth as <token>:api_token.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 11
- WRITE SIGNALS
- 8
- HIGH IMPACT
- 4
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Toggl Track.