Get the product details for this workspace

product.getReadsOnly looks things up; never changes your workspace.

What it does

Reads the product description stored on the connected workspace. In Test Maze the "product" is the workspace itself, so there is exactly one per connection and no id to pass. Use it at the start of planning work (writing features, user stories or test cases) so you know what the app is for and who uses it. Returns id, name, description, vision, problemStatement, targetUsers, productOwnerId, lifecycleStage (discovery, beta, live or sunset), launchedAt, sunsetAt, defaultBranch, repoUrl and status. Empty fields come back null. Read-only. If the key fields are empty, fill them in with product.update (or project.initialize to draft them from the repo).

Ask your agent

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

  • “What does Test Maze know about my app so far?”
  • “Load the product context before we plan the next feature”

Inputs

None. The agent calls it with an empty object.

The MCP call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "product.get",
    "arguments": {}
  }
}

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.