Summary

We use AI assistants connected to ClickUp to automate our sprint metrics, through the public API and the official ClickUp MCP server. These tools can read tasks, lists and comments. They cannot read Sprint Reporting (Sprint Task Report, and the Burndown/Burnup and Velocity reports), because that data is not exposed through the API or the MCP. We ask that it be made available to AI integrations.

Current behavior

The MCP server and the public API have no endpoint or tool for sprint reports.

An AI assistant only sees the current state of each task. It cannot see the committed snapshot taken at sprint confirmation or the Added/Removed/Completed/Remaining breakdown that ClickUp already calculates and shows on screen.

Rebuilding this data from task history gives wrong results: moving a task between lists does not update date_updated, and closed sprints cannot be recovered at all.

ClickUp Brain also cannot answer questions such as "how many points were added to Sprint 27 after confirmation?"

Why it matters

Our product team runs an automated routine with an AI assistant that collects sprint metrics (committed vs. completed, scope added mid-sprint, carry-over) and publishes them for leadership. Sprint Reporting is the only reliable source for these numbers. Without access, the routine depends on someone copying values from the screen by hand.

Requested improvement

Public API endpoint(s) that return the Sprint Task Report for a given sprint: per-sprint totals, plus a per-task list with ID, name, assignee, points, status, category (Committed / Added / Removed / Completed / Remaining / After sprint close) and the date the task entered or left the sprint. This must include the committed snapshot at confirmation time.

The same data exposed as tools in the official ClickUp MCP server, so assistants such as Claude, ChatGPT and Copilot can query it with the user's permissions.

Velocity and Burndown/Burnup data through the same endpoints, covering several sprints at once.

(Nice to have) ClickUp Brain able to answer questions using Sprint Reporting data.

Acceptance criteria

Given a confirmed sprint, when an AI assistant calls the API or MCP for that sprint's report, then it receives every task with its category, and the totals match the cards shown in Sprint Reporting.

Given a sprint that is already closed, the response still returns the committed snapshot as it was at confirmation.

The response uses the effort measure set for the report (sprint points, time estimate or task count).

Access follows the same permissions as the user or token that authenticated the request.

Environment

Sprints ClickApp, Sprint Reporting → Sprint Task Report. Effort measure: Sprint Points. Sprint length: 2 weeks. Clients: public API v2 and the ClickUp MCP server.