MCP Server: Add Sprint Points (read & write) to task tools
Sarah Van den berghe
The ClickUp MCP server currently doesn't expose Sprint Points when reading or writing tasks. The points field is missing from both the Get Task response and the Update/Create Task tool parameters.
The REST API already fully supports this (points as a top-level field on GET /v2/task/{id}, PUT /v2/task/{id}, and POST /v2/list/{id}/task), so this seems like a gap in MCP tool coverage rather than a missing platform capability.
Sprint Points are essential for sprint planning and workload tracking. Without MCP support, AI agents (e.g. Claude, Cursor) can't read or set points on tasks, forcing teams to fall back to manual updates or direct API calls.
Request: Surface the points field in the MCP's task read/write tools, matching the existing REST API behavior.
Log In
Kendra Tolbert
Same issue here. We looked at a task that clearly shows 4 Sprint Points in the ClickUp UI, but when we pull that same task through the API, Sprint Points doesn't show up at all, it's just missing from the response. We also can't set Sprint Points when creating or updating a task through the API, there's no option for it there either.
What's interesting is your own feedback board shows Sprint Points support was already added to the core API a while back. So this looks like the MCP tool just hasn't caught up to that yet, not a limitation of ClickUp as a whole.
Would love to see this closed out. We rely on Sprint Points to track team capacity across every project we run, so not having it available here is a real gap for us.
Chris Scribner
This would be an enormous help for me too. It is the one gap in my workflow between Claude and Clickup right now.