I use ClickUp as my actual timecard, and I would really like to be able to manage it through the API and ClickUp’s MCP server. Right now, the time-tracking support is only partial. The public API has several time-tracking endpoints, but it still does not let me reliably perform all of the same actions that I can perform through the ClickUp interface. Active, in-progress timers are particularly limited. The MCP server exposes an even smaller subset of the available functionality. I would like the API and MCP server to support the complete timecard workflow, including: Viewing all of my time entries for a day or date range, including taskless entries Starting, stopping, and viewing an active timer Editing an active timer without having to stop it and reconstruct the entry Changing the task associated with an active or completed entry Changing the start time, end time, duration, description, tags, and billable status Stopping an active timer at a specified time rather than only at the current moment Creating taskless time entries Editing and deleting completed entries Finding gaps, overlaps, or duplicate entries Summarizing hours for a day or week The goal is to be able to make a request such as: “Show me today’s timecard, move the active timer to the correct task, change its start time to 9:15, add a 30-minute meeting from this morning, and tell me how much time is still missing from an eight-hour day.” At the moment, I can do pieces of this through the API, pieces through MCP, and the rest only through the ClickUp interface. I would like time tracking to be treated as a complete, manageable resource across both the public API and MCP server.