BrowserStack MCP
Provisions cross-browser, cross-device test runners on demand for EVAN's Playwright suites. Captures device-specific failure evidence for SARA. Status
Beta. Currently supports Playwright + Selenium projects on the BrowserStack Automate platform. Cypress + Appium support is on the roadmap.
What flows in
·Available browsers + OS combinations
·Available real devices (mobile)
·Session metadata (logs, screenshots, video) for failed tests
·Network HARs from runs
What flows out
·Test runs (parallelized across configured browsers)
·Test session metadata (associating with EVAN run IDs and Jira / TestRail tickets) ·Build records (for trend tracking across browsers)
Browser matrix
EVAN can be configured to run against: ·Tier 1 — latest Chrome, Firefox, Safari, Edge on macOS + Windows
·Tier 2 — Tier 1 + Chrome / Firefox at version-1 (one major version back)
·Tier 3 — Tier 2 + IE11 / older Safari (for legacy enterprise targets)
·Mobile — latest iOS Safari, Android Chrome on real devices
Tier choice is per-project. Tier 1 is sufficient for most modern web apps; Tier 3 is needed only for products with explicit legacy support.
Parallelization
A 200-test EVAN suite runs in ~5 minutes on a 20-parallel BrowserStack plan. The connector batches tests intelligently: ·Slow tests run first (so they finish before the run window expires)
·Tests with shared setup are grouped on the same VM (cuts overhead)
·Flaky tests run twice and are marked accordingly
Failure evidence
→When a test fails, the connector pulls:
·A screenshot at the moment of failure
·The full session video
·The browser console log
·The network HAR
This evidence is uploaded toEvidence Capture and linked from the EVAN report. Engineers reviewing a failure see the same thing they'd see in BrowserStack's UI, but in their normal review flow. Cost awareness
→BrowserStack runs cost real money. The connector tracks per-project minute usage and surfaces a warning when approaching the plan's monthly cap.
By default, BrowserStack runs are gated behind an explicit --cross-browser flag — the default EVAN flow runs locally to avoid burning the cap on every commit. Authentication
Username + access key (BrowserStack's standard auth). Keys are stored encrypted, scoped per project.
Server
mcp://browserstack.com/mcp
Vendor
BrowserStack.
Limitations
·iOS Safari sessions can be flaky during peak hours; the connector retries once before reporting a failure
·Mobile real-device sessions are limited to 10 minutes — long suites are split automatically