Read your Track profile, accessible workspaces and a known project with your own Toggl Track API token. Profile reads omit the token and other authentication metadata. These three commands do not start timers, change projects, fetch reports or use the separate Toggl Focus API.
What you can do (3)
What you can do
Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
Read my Toggl Track profile — toggl.user.get |
Read |
List my Toggl Track workspaces — toggl.workspaces.list |
Read |
Read a Toggl Track project — toggl.projects.get |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Toggl Track, then enter the issued values in the connection form below.
- Sign in to Toggl Track and open Profile (track.toggl.com/profile). Copy your API token into Toggl Track API token in this connection. It authenticates as your Track user and inherits that user’s workspace permissions; it is not your account password or a Toggl Focus bearer token. Select user.get or workspaces.list and save, then create an Tooluse.net API key scoped to the selected commands for your client. Use a returned workspace ID and a project ID from Track with projects.get. Regenerate the token in your Toggl profile and replace it here when needed. No managed OAuth or automatic renewal is provided.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Toggl Track API token | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
Read my Toggl Track profile — toggl.user.get
Read your user ID, full name, time zone and default workspace ID without related collections. The provider also returns its API token and authentication metadata; this command deliberately excludes them. This reads Toggl Track, not the separate Toggl Focus API.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
List my Toggl Track workspaces — toggl.workspaces.list
Read IDs, names, organization IDs and premium status for workspaces visible to this Track user. This provider endpoint returns a single collection without a page parameter. No related people, billing details or time entries are returned; large responses fail the existing 512 KiB bound.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read a Toggl Track project — toggl.projects.get
Read the identity and state of one known project in one known workspace. Returns ID, name, workspace/client IDs, active, private and billable flags. Obtain workspace_id from workspaces.list and project_id from Toggl Track. No project changes, rates, reports or time entries are supported.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.workspace_id |
integer | Required | A workspace ID returned by workspaces.list. | minimum: 1; maximum: 9007199254740991 |
path.project_id |
integer | Required | The project ID from Toggl Track. | minimum: 1; maximum: 9007199254740991 |
Full JSON Schema
Example input
{
"path": {
"workspace_id": 10,
"project_id": 42
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.