Kiwi for Cypress
Have the agent on a Kiwi step read Cypress Cloud runs and their failed and flaky tests through the Cypress Cloud MCP server.
- Your agent works in Cypress through its own connection. Kiwi does not call Cypress and never holds its credentials.
- A workflow skill can list Cypress among the tools it requires. When you supply your agent's available tools to a skill check and Cypress is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Cypress, 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 Cypress connection, with
report_configuration. - The agent submits links to its work in Cypress as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in Cypress
- List recent Cypress Cloud runs and the specs and tests in each one.
- Get the failed tests of a run with their errors and screenshots.
- Find tests that Cypress Cloud has marked as flaky.
- Read the accessibility and UI coverage reports for a run.
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 Cypress
Add the Cypress MCP server to your agent with this URL. The credentials stay with your agent.
https://mcp.cypress.io/mcpExample skill
Publish instructions like these as a workflow skill that lists Cypress among its required tools.
Start from the branch and the Cypress Cloud project in the assignment. Find the latest run for the branch and get its failed and flaky tests. Read each failure's error and screenshot and fix the cause in the code. Submit the run link and a note per failed test as the step's outputs. If no run exists for the branch, stop and report a blocker to the step owner; the assigned reviewer decides on tests marked flaky.