Sprint Tools

Four tools for sprint management: create, update, complete, and delete.

Sprint Lifecycle

Sprints follow a strict lifecycle:

Planned (0) → Active (1) → Completed (2)

• A project can have only one active sprint at a time
• Sprints can be moved from Planned to Active via update-sprint
• Completing a sprint must use complete-sprint (not update-sprint)
• Incomplete issues can be moved to a target sprint or unassigned on completion

create-sprint

Create a new sprint in a project.

Parameters

Parameter	Type	Required	Description
project_id	integer	Yes	The project to create the sprint in
title	string	Yes	Sprint title (max 255 characters)
start	date	Yes	Start date (ISO 8601, e.g., 2026-04-01)
end	date	Yes	End date (ISO 8601, e.g., 2026-04-14). Must be after start.

Behavior

• Created with Planned status (0)
• Returns sprint with ID, title, dates, status, and issue count

Example Prompt

Create a two-week sprint called "Sprint 12" in the kendo project starting next Monday

update-sprint

Update an existing sprint's title, dates, or status.

Parameters

Parameter	Type	Required	Description
sprint_id	integer	Yes	The sprint to update
title	string	No	New title (max 255 characters)
start	date	No	New start date (ISO 8601)
end	date	No	New end date (ISO 8601). Must be after start.
status	integer	No	0 Planned, 1 Active. Cannot set to 2 Completed — use complete-sprint.

Behavior

• Only provided fields are updated
• Date validation uses merged values (new dates combined with existing ones)
• Cannot change status to Completed — use complete-sprint instead, which handles incomplete issue reassignment

Example Prompt

Activate Sprint 12, we're starting it today

complete-sprint

Complete the active sprint in a project, with optional reassignment of incomplete issues.

Parameters

Parameter	Type	Required	Description
project_id	integer	Yes	The project whose active sprint to complete
sprint_id	integer	No	Target sprint for incomplete issues. If omitted, incomplete issues become unassigned from any sprint.

Behavior

• Finds the currently active sprint in the project
• Issues in the Done lane (last lane) are considered complete
• Incomplete issues (not in Done) are either:
  • Moved to the target sprint (if sprint_id is provided)
  • Unassigned from any sprint (if sprint_id is omitted)
• The sprint is marked as Completed
• Throws an error if no active sprint exists

Example Prompt

Complete the current sprint in the kendo project. Move anything that's not done into Sprint 13.

delete-sprint

Permanently delete a planned sprint. Only sprints with status "Planned" can be deleted.

Destructive

This action cannot be undone. The sprint is permanently removed.

Parameters

Parameter	Type	Required	Description
sprint_id	integer	Yes	The ID of the sprint to delete

Behavior

• Only Planned sprints can be deleted — active or completed sprints must go through the normal lifecycle
• Issues in the sprint become unassigned from any sprint
• Requires Sprints: Delete permission
• Returns confirmation with the deleted sprint's details

Example Prompt

Delete Sprint 14 — we decided to merge it with Sprint 13 instead

assign-issues-to-sprint

Bulk assign multiple issues to a sprint, move them between sprints, or remove them from any sprint in a single MCP call. Designed to replace looping update-issue for sprint membership changes — one transaction, one batched SQL UPDATE, one broadcast, at most one audit-log row per touched issue (no-ops skipped).

Prefer this over looping update-issue

Whenever the only change is sprint membership, call this tool once with all issue ids. It is dramatically more efficient than calling update-issue per issue and produces a single broadcast frame for subscribed pages.

Parameters

Parameter	Type	Required	Description
project_id	integer	Yes	The project that owns the issues and sprint
issue_ids	integer[]	Yes	Issue IDs to assign (1–100). All ids must belong to the named project.
sprint_id	integer | null	No	Target sprint ID. Pass null (or omit) to remove the issues from any sprint.

Behavior

• All issue_ids must belong to project_id — mixed-project requests are rejected with an explicit error
• The target sprint (when not null) must belong to the same project
• Existing order and lane_id values are preserved — only sprint_id and updated_at are written
• Issues already in the target sprint are no-ops: the SQL UPDATE still runs but the audit dedup skips the row
• Returns updated_count, the resolved sprint_id, and the echoed issue_ids
• Requires Issues: Update permission on the project (the same permission that powers drag-drop board updates)
• The broadcast updates pages already showing the affected issues; pages whose scope didn't include the issue before need a refresh to load it

Example Prompts

Assign issues 412, 415, and 418 to Sprint 12 in the kendo project

Move all backlog issues tagged frontend-only into the active sprint

Remove issues 501–510 from their current sprint and put them back on the backlog

See Also

• Resources — Read sprint data via kendo://projects/{id}/sprints
• Sprints Guide — Understanding sprint lifecycle and planning
• Sprints API — REST endpoints for sprint management