TrackWork MCP and REST API integration
Connect your TrackWork account to compatible MCP clients with a personal API token, or access project data through REST.
Last updated:
1. Create a personal API token
Create an API token in Settings in your dashboard. Its plain-text value is shown only once. The token grants access to your account's data; do not include it in public repositories, chats or client links. Revoke unused or exposed tokens in Settings.
2. Connect an MCP client
Set the server URL and Authorization header in an MCP client that supports Streamable HTTP. Replace YOUR_TOKEN below with your own token only in your local client configuration. Authentication and transport support vary by client.
{
"mcpServers": {
"trackwork": {
"url": "https://trackwork.app/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}3. Try a read-only REST request
The same Bearer token works with /api/v1 endpoints. The examples below only read the account and project list. Set TRACKWORK_API_TOKEN in your secure local environment.
curl https://trackwork.app/api/v1/me \
-H "Authorization: Bearer $TRACKWORK_API_TOKEN"
curl https://trackwork.app/api/v1/projects \
-H "Authorization: Bearer $TRACKWORK_API_TOKEN"Supported operations
REST v1 includes listing the account and clients; listing, creating and updating projects; adding and updating steps and subtasks; and adding payment records and today's status. Write operations change real data in your account. Verify the target project in your automations.
- GET /api/v1/me
- GET /api/v1/clients
- GET veya POST /api/v1/projects
- GET veya PATCH /api/v1/projects/:id
- POST /api/v1/projects/:id/steps
- PATCH /api/v1/steps/:id
- POST /api/v1/steps/:id/sub-steps
- PATCH /api/v1/sub-steps/:id
- POST /api/v1/projects/:id/payments
- POST /api/v1/today-status