Kiwi
Kiwi

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 agentsQuickstart

  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

  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.
Get startedRead the setup guide