List exploration sessions

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

What it does

Lists recent exploration sessions in the connected workspace, from every user, most recently updated first. Use it to find a session id to resume, read or turn into test cases. Each row has id, status, name, goal, featureId, startUrl, steps, pages, errors, verifiedShare (share of judged steps the server could confirm, 0–1), startedAt, lastObservationAt, endedAt and a testmaze:// uri. Next: exploration.get for the full record, or exploration.to_cases.

Ask your agent

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

  • “What explorations have we run so far?”
  • “Is there an exploration still in progress?”

Inputs

NameTypeDescription
status
optional
enumOnly sessions in this state. active: still running. completed: finished normally. abandoned: stopped early or idle for 30 minutes. saved: recordings made in the Test Maze web assistant. Default: all.
Allowed: activecompletedabandonedsaved
limit
optional
integerMost sessions to return (1–100, default 20).

The MCP call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "exploration.list",
    "arguments": {
      "status": "active"
    }
  }
}

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.