Labsco
MCP SERVER · OFFICIAL PROJECT

BrowserStack

by browserstack ↗

Put BrowserStack's real devices behind the client you write in: set up the SDK in your project, scan a page that sits behind a login for WCAG issues, review Percy's visual diffs, and pull logs, screenshots and root-cause analysis when a build goes red.

Automated Testing & QA✓ Verified
Summary
The triage tools earn their place faster than the setup ones: a red build turns into logs, screenshots and a suggested fix in the same conversation.

Several tools do something with the result rather than just fetching it. The self-healing pair hands back locator pairs bundled with the source so your editor changes only the call sites that matter instead of running a blind find-and-replace, and the root-cause tool suggests fixes it never applies on its own. The counterpart is that the setup tools write into your project — one of them edits the test files you point it at — so aim them at a checkout you are willing to have changed.

What it is

BrowserStack's own server over its cloud: 44 tools spanning Automate and App Automate runs, Percy visual testing, accessibility scans and Test Management.

What you get
  • SDK setup written into your project for web suites and for Appium mobile suites, plus direct upload of pre-built Espresso and XCUITest tests
  • Manual live sessions on a chosen browser, OS version or phone — including a site running on your own localhost — with screenshots taken of an app on the device
  • Accessibility scans that sign in first through a stored form-based or basic-auth configuration, returning a local CSV report path and issues paged with a cursor
  • Percy integrated into a project, widened across existing tests, run as a build, then its visual changes summarised and the build approved or rejected
  • Test Management as data: projects, folders, cases, templates, runs, results, plans and sub-plans, including cases generated from an uploaded requirements document
  • Failure triage after a run: session logs by type, Automate screenshots, build insights combined with quality-gate results, and root-cause analysis that suggests fixes without applying them
  • Self-healed selectors from one session or a whole build, bundled with the test source into an edit plan your own editor applies
Requirements

A BrowserStack account, with BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY in the environment, and Node 18 or newer — the project recommends the current LTS. A checkout the setup tools may write into, and a compiled .apk or .ipa for the app-side tools. AGPL-3.0, which is worth knowing if you redistribute it.

Setup effort

One command plus a key — npx -y @browserstack/mcp-server@latest, then supply credentials