Create a release, sprint or milestone

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

What it does

Creates a time-boxed bucket to plan work into. Pick the kind: release = a version you ship to users ("v2.0"); sprint = a short fixed work cycle ("Sprint 23", usually 1 to 2 weeks); milestone = a named goal that is not a shipment ("Public beta"). Call project.whoami to confirm the workspace and release.list first, since duplicate names are not blocked. It starts with status "planned". Returns {success, data: the saved release including its id, uri}. Next: link features with feature.set_release, pass the id to testrun.create to tag test runs with it, and call release.ship when it goes out.

Ask your agent

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

  • “Create a v2.0 release targeting the end of June”
  • “Start Sprint 24 from Monday for two weeks”
  • “Add a milestone for the public beta”

Inputs

NameTypeDescription
name
required
stringDisplay name, up to 128 characters. Examples: "v2.0", "Sprint 24", "Public beta".
kind
optional
enumrelease (default) = a version shipped to users; sprint = a short fixed work cycle; milestone = a named goal or checkpoint that is not a shipment.
Allowed: releasesprintmilestone
startDate
optional
stringWhen work starts, as YYYY-MM-DD. Example: "2026-06-01".
targetDate
optional
stringWhen it is meant to ship or end, as YYYY-MM-DD. Example: "2026-06-30".
releaseNotesUrl
optional
stringLink to the release notes or changelog, up to 255 characters. Example: "https://github.com/acme/app/releases/tag/v2.0".

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.create",
    "arguments": {
      "name": "<name>"
    }
  }
}

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.