MCP tools: Sprints and weekly planning

Create, fill and evaluate sprints, fetch the AI sprint suggestion and read the weekly plan with utilization.

Prerequisites
  • Sprints or Planning module enabled.
  • Backlog tasks from which a sprint should be built.

list_sprints

Lists sprints of the organization, newest first, each with its task count (taskCount) and total estimated hours (estimatedHours). Requirements: role Viewer or higher, key scope "read" or higher, module "Sprints" enabled.

status
Optional · string · planning | active | completed | cancelled — Only sprints with this status.
projectId
Optional · string — Only sprints of this project.

get_sprint

Returns a sprint with all its tasks, including planned (estimatedHours) and actual hours (actualHours from time entries), plus statistics: totalTasks, completedTasks, totalEstimatedHours, totalActualHours and capacityUsedPercent (planned versus capacity). Requirements: role Viewer or higher, key scope "read" or higher, module "Sprints" enabled.

id
Required · string — ID of the sprint.

create_sprint

Creates a sprint. Only the name is required; without further input the sprint starts with status planning. Requirements: role Member or higher, key scope "write" or higher, module "Sprints" enabled.

name
Required · string — Sprint name.
goal
Optional · string — Sprint goal description.
startDate
Optional · string — Start date (ISO 8601, YYYY-MM-DD).
endDate
Optional · string — End date (ISO 8601, YYYY-MM-DD).
capacityHours
Optional · number — Total team capacity for the sprint in hours (planned).
projectId
Optional · string — Optional project scope.
status
Optional · string · planning | active | completed | cancelled — Initial status. Default: planning.

update_sprint

Updates a sprint. Use it to start (active) or finish (completed) a sprint and to change dates, goal or capacity. Requirements: role Member or higher, key scope "write" or higher, module "Sprints" enabled.

id
Required · string — ID of the sprint.
name
Optional · string — New name.
goal
Optional · string — Sprint goal description.
startDate
Optional · string — Start date (ISO 8601, YYYY-MM-DD).
endDate
Optional · string — End date (ISO 8601, YYYY-MM-DD).
capacityHours
Optional · number — Total team capacity for the sprint in hours (planned).
projectId
Optional · string — New project scope.
status
Optional · string · planning | active | completed | cancelled — New status.

delete_sprint

Permanently deletes a sprint and removes all its task assignments; the tasks themselves are not deleted. Requires at least the Admin role and a key with the delete scope. Requirements: role Admin or higher, key scope "delete" or higher, module "Sprints" enabled.

id
Required · string — ID of the sprint.

add_task_to_sprint

Adds an existing task to a sprint (adding twice is harmless) and sets the sprint reference on the task. The tool checks that the sprint belongs to the organization. Requirements: role Member or higher, key scope "write" or higher, module "Sprints" enabled.

sprintId
Required · string — ID of the sprint.
taskId
Required · string — ID of the task to add.

remove_task_from_sprint

Removes a task from a sprint and clears the sprint reference on the task. The task itself remains. Requirements: role Member or higher, key scope "write" or higher, module "Sprints" enabled.

sprintId
Required · string — ID of the sprint.
taskId
Required · string — ID of the task to remove.

suggest_sprint_plan

AI sprint planning: an AI planner composes the sprint from the open backlog, weighing priority, deadlines, sprint goal and effort (manual hours, similar-task estimates or its own realistic estimates) within the sprint capacity. If the AI is unavailable, a rule-based plan is used (method="rules"). The tool changes nothing – apply the suggestion with add_task_to_sprint. Your task visibility rules apply. The result is AI-generated. Requirements: role Viewer or higher, key scope "read" or higher, module "Sprints" enabled.

sprintId
Required · string — ID of the sprint.

get_planning_week

Shows the weekly plan: for each member the tasks assigned to the week plus utilization – hoursPerWeek (stored capacity, otherwise 40), usedHours (sum of estimated hours) and utilizationPct. Requirements: role Viewer or higher, key scope "read" or higher, module "Planning" enabled.

week
Optional · string — Monday of the week as ISO date (e.g. 2026-06-30). Default: current week.

list_unscheduled_tasks

Lists tasks that are not yet assigned to a week in the planning schedule. The tool does not filter by status, so completed tasks appear too. Requirements: role Viewer or higher, key scope "read" or higher, module "Planning" enabled.

limit
Optional · number — Maximum number of results (default 30, max 100).

Common pitfalls

  • The suggestion changes nothing

    suggest_sprint_plan is read-only. Apply the suggestion with add_task_to_sprint (and set the sprint to active via update_sprint).

  • Deleting only removes assignments

    delete_sprint deletes the sprint and its assignments; the tasks themselves remain.

  • Unscheduled does not mean open

    list_unscheduled_tasks does not filter by status and therefore also shows completed tasks.

Keep reading

Still have a question or a problem?

Visit support

Last reviewed on 2026-09-26