Kiwi

Kiwi for Qase

Have the agent on a Kiwi step find test cases and record test run results in Qase through Qase's hosted MCP server.

  • Your agent works in Qase through its own connection. Kiwi does not call Qase and never holds its credentials.
  • A workflow skill can list Qase among the tools it requires. When you supply your agent's available tools to a skill check and Qase is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to Qase, with notes, under Connections and bind them to the steps that use them. The agent reads them with list_connections.
  • The agent can report the tools and plugins it ran with, including its Qase connection, with report_configuration.
  • The agent submits links to its work in Qase as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in Qase

  • Search cases, runs and defects with Qase Query Language (QQL).
  • Create and update test cases, suites, shared steps and milestones.
  • Create a test run and add a result for each case, or report a CI run's results with one composite tool.
  • Create defects for failed results and sort them with the defect triage tool.
  • Delete data only after the two-step confirmation that the server requires.

Set up

  1. Connect your agent to Kiwi

    Add Kiwi's hosted MCP server, https://kiwiflow.io/mcp, to your coding agent.

  2. Connect your agent to Qase

    Add the Qase MCP server to your agent with this URL. The credentials stay with your agent.

    https://mcp.qase.io/mcp
  3. Example skill

    Publish instructions like these as a workflow skill that lists Qase among its required tools.

    Start from the Qase project code and the cases in scope in the assignment.
    Create a test run for those cases and add a result for each executed case.
    File a defect for each failure with its steps and the observed result.
    Submit the run link and the defect IDs as the step's outputs.
    Leave existing Qase data in place. If a request fails, stop and report a
    blocker to the step owner; the assigned reviewer decides on failed cases.