List features and user stories

feature.listReadsOnly looks things up; never changes your workspace.

What it does

Lists the features, sub-features, user stories and regression suites in the connected workspace. In Test Maze all four are stored as test suites (a named group of test cases), told apart by type: feature = a capability of the product ("Checkout"); sub-feature = a smaller part of a feature ("Apply a coupon"); user-story = one user need inside a feature, written as "As a ..., I want ..., so that ..."; regression = a plain group of tests with no product meaning. Call this before feature.create or userstory.create so you do not create duplicates, and to find the id other tools need. Returns 20 rows per page, newest first: {items: [{id, uri, title, type, description, lifecycleStage, parentFeatureId, releaseId}], page, totalPages, totalItems}. Read-only.

Ask your agent

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

  • “What features do we already have in Test Maze?”
  • “Is there already a feature for checkout?”
  • “Show me the user stories we have written”

Inputs

NameTypeDescription
type
optional
enumOnly return one kind. feature = product capability; sub-feature = part of a feature; user-story = one user need under a feature; regression = plain test group. Omit to list all kinds.
Allowed: featuresub-featureuser-storyregression
title
optional
stringCase-insensitive text to match anywhere in the title. Example: "checkout" also matches "Guest Checkout".
page
optional
integerPage number, starting at 1 (default 1). Each page holds 20 rows; use totalPages from the result to know when to stop.

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.list",
    "arguments": {
      "type": "feature"
    }
  }
}

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.