Kiwi for Sauce Labs
Have the agent on a Kiwi step find failing Sauce Labs jobs and their root causes through the Sauce Labs MCP server.
- Your agent works in Sauce Labs through its own connection. Kiwi does not call Sauce Labs and never holds its credentials.
- A workflow skill can list Sauce Labs among the tools it requires. When you supply your agent's available tools to a skill check and Sauce Labs is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Sauce Labs, 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 Sauce Labs connection, with
report_configuration. - The agent submits links to its work in Sauce Labs as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in Sauce Labs
- List recent jobs and builds and read the details of a job.
- Get the failing tests in a build and the error trends across builds.
- Get the root causes of failed jobs and their test assets, such as logs.
- Check which browsers and devices the tests cover.
- Upload an app file to Sauce Labs storage for testing.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to Sauce Labs
Add the Sauce Labs MCP server to your agent with this URL. The credentials stay with your agent.
https://mcp.saucelabs.comExample skill
Publish instructions like these as a workflow skill that lists Sauce Labs among its required tools.
Start from the Sauce Labs build named in the assignment. List its failing tests and get the root causes of each failed job. Fix the cause in the tests or the code and note which job showed it. Submit the job links and the fix for each failure as the step's outputs. If a job's assets are unavailable, stop and report a blocker to the step owner; the assigned reviewer decides on failures left open.