Fix E2E tests to use namespaced tool names and handle wrapped API responses

[Copilot]

E2E tests failed because they used pre-namespace tool names and expected raw JSON responses, but the generated MCP server uses namespaced tools (e.g., settings_system_backendVersion) and wraps responses in "API Response (Status: XXX):\n{...}" format.

Changes

Tool name updates:

• Updated all tool invocations to use namespaced format generated by openapi-mcp-generator
• backendVersion → settings_system_backendVersion
• listJobs → job_list_listJobs
• getUser → user_profile_whoami
• listWorkspaces → workspace_list_listUserWorkspaces
• Plus 4 other tools updated similarly

Response parsing:

• Added regex extraction for wrapped JSON: /API Response \(Status: \d+\):\n([\s\S]*)/
• Handle plain text responses (e.g., version endpoint returns "CE v1.580.0...")
• Removed checks for non-existent isError property

Data structure fixes:

• Workspace listing returns { email, workspaces: [] } not an array
• Scripts don't include workspace_id field

Example change:

// Before
const response = await mcpClient.request({
  method: "tools/call",
  params: { name: "listJobs", arguments: { workspace } }
});
const result = JSON.parse(response.content[0].text);

// After
const response = await mcpClient.request({
  method: "tools/call",
  params: { name: "job_list_listJobs", arguments: { workspace } }
});
const resultText = response.content[0].text;
const jsonMatch = resultText.match(/API Response \(Status: \d+\):\n([\s\S]*)/);
const result = jsonMatch ? JSON.parse(jsonMatch[1]) : null;

Tests: 27/27 passing (was 12 failures)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Build workflow failed for latest version after recent changs</issue_title>
<issue_description>See https://github.com/rothnic/windmill-mcp/actions/runs/19509122419/job/55843726100

Notes:

• The build should fail if the integration tests don't pass

Key things to review:

• are the env variables all setup and available for running the integration tests (maybe the github project needs env variables added, or should they just be set in the workflow since they aren't secret, they are just for testing)</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Build workflow failed for latest version after recent changs #26

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.