Check which workspace this connection uses

project.whoamiReadsOnly looks things up; never changes your workspace.

What it does

Tells you which Test Maze workspace this connection reads from and writes to, which user your changes are credited to, and which access token was used. A workspace holds one product: its features, test cases, test runs, releases and metrics. Call this FIRST in a new session, and again whenever you are unsure (after switching project folders or re-running npx @testmaze/mcp init). Show the workspace name to the user and get a yes before creating or changing anything, because every write lands in this workspace. Returns space {id, name, description, lifecycleStage, repoUrl, defaultBranch, uri}, user {id, name, email}, token {id, name} (null when no token was used) and a one-line hint. If space.name is null the workspace could not be loaded (the token may belong to a deleted workspace). Read-only. Next: product.get for the full product context.

Ask your agent

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

  • “Which Test Maze workspace am I connected to?”
  • “Before you add anything, check you are pointed at the right project”
  • “Who will these changes show up as?”

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": "project.whoami",
    "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.