Cancel a release

release.cancelChanges dataCreates, updates or deletes something in your workspace.

What it does

Marks a release, sprint or milestone as cancelled, for when the plan is dropped and it will not ship. Only the status changes: linked features keep their link (move them with feature.set_release) and nothing is deleted. No tool sets it back to planned, so confirm with the user first. The release must belong to the connected workspace. Returns {success, data: the updated release}.

Ask your agent

You don’t call release.cancel yourself. Say something like this to Claude Code, Cursor or another MCP-connected agent:

  • “Cancel the v2.1 release, we are not doing it”
  • “Drop the investor demo milestone”

Inputs

NameTypeDescription
releaseId
required
stringId of the release, sprint or milestone to cancel (the id from release.list).

The MCP call

What the agent’s MCP client sends (placeholders in angle brackets):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "release.cancel",
    "arguments": {
      "releaseId": "<releaseId>"
    }
  }
}

Connect your agent

npx -y @testmaze/mcp init tmt_xxx
claude mcp add tm --scope project -- npx -y @testmaze/mcp

Create the token in your Test Maze workspace under Settings → MCP. Setup for Cursor, Cline, Gemini CLI and Codex CLI is shown there too.