Plan a feature into a release

What it does

Links a feature (or user story) to the release, sprint or milestone it is planned to ship in, or removes that link. Use it when the plan changes, for example moving "Guest checkout" from Sprint 23 to Sprint 24. Get the feature id from feature.list and the release id from release.list (create one with release.create if needed). A suite has at most one release; setting a new one replaces the old. Pass releaseId: null to unlink. The feature must belong to the connected workspace; the release id is stored as given and is not checked, so take it from release.list. Returns {success, message, data: the updated suite}.

Ask your agent

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

• “Put guest checkout into the June release”
• “Move the search feature to next sprint”
• “Take password reset out of this release”

Inputs

The MCP call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "feature.set_release",
    "arguments": {
      "suiteId": "<suiteId>",
      "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.

More features & user stories tools

• List features and user stories feature.list
• Create a feature feature.create
• Create a user story under a feature userstory.create
• Move a feature or story to a new stage feature.set_lifecycle