---
title: "Kiwi for BrowserStack"
description: "Have the agent on a Kiwi step run tests on BrowserStack Automate and investigate failed sessions through BrowserStack's MCP server."
canonical: "https://kiwiflow.io/integrations/browserstack"
---

# Kiwi for BrowserStack

Have the agent on a Kiwi step run tests on BrowserStack Automate and investigate failed sessions through BrowserStack's MCP server.

- Your agent works in BrowserStack through its own connection. Kiwi does not call BrowserStack and never holds its credentials.
- A workflow skill can list BrowserStack among the tools it requires. When you supply your agent's available tools to a skill check and BrowserStack is not among them, the check reports `SK15-UNSUPPORTED-TOOL`.
- A project Admin can add links to BrowserStack, 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 BrowserStack connection, with `report_configuration`.
- The agent submits links to its work in BrowserStack as the step's outputs. People review them, and sign-off stays with the people your workflow names.

## What your agent can do in BrowserStack

- Set up a project's existing test suite to run on BrowserStack Automate.
- List Automate sessions and fetch their screenshots.
- Get the failure logs and a root cause analysis for a failed session.
- Fetch the selectors that BrowserStack self-healed during a run so the tests can be updated.

## Set up

### 1. Connect your agent to Kiwi

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

- [Coding agents](https://kiwiflow.io/integrations#agent)
- [Quickstart](https://docs.kiwiflow.io/quickstart#connect-your-agent)

### 2. Connect your agent to BrowserStack

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

```
https://mcp.browserstack.com/mcp
```

- [BrowserStack documentation](https://www.browserstack.com/docs/browserstack-mcp-server/tools/automate)

### 3. Example skill

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

```
Start from the build name and the failed session IDs in the assignment.
Get the failure logs and root cause analysis for each failed session.
Fix the cause in the tests or the code and note what changed.
Submit the session links and a note per failure as the step's outputs.
If BrowserStack returns no logs, stop and report a blocker to the step
owner; the assigned reviewer decides on failures that remain.
```

## More testing integrations

- [Kiwi for Playwright](https://kiwiflow.io/integrations/playwright.md): Have the agent on a Kiwi step drive a browser through Playwright MCP to check a change in the running app and capture what it saw.
- [Kiwi for Postman](https://kiwiflow.io/integrations/postman.md): Have the agent on a Kiwi step update Postman collections, specifications and environments for an API change through Postman's remote MCP server.
- [Kiwi for Cypress](https://kiwiflow.io/integrations/cypress.md): Have the agent on a Kiwi step read Cypress Cloud runs and their failed and flaky tests through the Cypress Cloud MCP server.
- [Kiwi for Appium](https://kiwiflow.io/integrations/appium.md): Have the agent on a Kiwi step drive a mobile app on a device or emulator through Appium MCP and capture what it observed.
- [Kiwi for Grafana k6](https://kiwiflow.io/integrations/k6.md): Have the agent on a Kiwi step write, validate and run Grafana k6 load test scripts through the k6 MCP server.
- [Kiwi for Sauce Labs](https://kiwiflow.io/integrations/sauce-labs.md): Have the agent on a Kiwi step find failing Sauce Labs jobs and their root causes through the Sauce Labs MCP server.
- [Kiwi for TestMu AI](https://kiwiflow.io/integrations/testmu-ai.md): Have the agent on a Kiwi step triage failed tests and check visual and accessibility results in TestMu AI, formerly LambdaTest, through its MCP server.
- [Kiwi for Chromatic](https://kiwiflow.io/integrations/chromatic.md): Have the agent on a Kiwi step publish a Storybook to Chromatic with the Chromatic CLI and report the visual changes it found.

- [Get started](https://kiwiflow.io/get-started)
- [Read the setup guide](https://docs.kiwiflow.io/other-tools)