accessibilityExpert
🚨 REQUIRED: Use this tool for any accessibility/a11y/WCAG questions. Do NOT answer accessibility questions directly - always use this tool.
LABSCO 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
USE CASES
01
Reproducing a bug that only happens on one phone
Open a live session with the build installed on the device the report names, drive it by hand, and capture what you see on the way through.
02
Scanning a page that sits behind a login for WCAG issues
Store the sign-in once as a form-based or basic-auth configuration, start the scan against that configuration, then page through the issues it found with a cursor.
03
Working out why last night's build went red
Resolve the build by project and name, list the tests that failed in it, pull the logs for one of them, and ask for the root-cause analysis before touching any code.
04
Repairing the tests that break every time a selector moves
Take the locator pairs BrowserStack healed during the run, for one session or for a whole build, and turn them into an edit plan that names the exact call sites — the plan is context for your editor, not a patch that applies itself.
05
Getting first-draft test cases out of a requirements document
Upload the document, generate cases from it into a folder, then read back what landed so the ones worth keeping can be edited and the rest dropped.
06
Reviewing what changed visually before a merge
Run the Percy build, read back the changes it detected against the previous build, and approve or reject the build once you have looked at them.
44 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
addPercySnapshotCommands
Adds Percy snapshot commands to the specified test files.
addTestResult
Add a test result to a specific test run via BrowserStack Test Management API.
createAccessibilityAuthConfig
Create an authentication configuration for accessibility scans. Supports both form-based and basic authentication.
createLCASteps
Generate Low Code Automation (LCA) steps for a test case in BrowserStack Test Management using the Low Code Automation Agent.
createProjectOrFolder
Create a project and/or folder in BrowserStack Test Management.
createTestCase
Use this tool to create a test case in BrowserStack Test Management.
createTestCasesFromFile
Generate test cases from a file in BrowserStack Test Management using the Test Case Generator AI Agent.
createTestRun
Create a test run in BrowserStack Test Management.
expandPercyVisualTesting
Set up or expand Percy visual testing configuration with comprehensive coverage for existing projects that might have Percy integrated. This supports both Percy Web Standalone and Percy Automate. Example prompts: Expand percy coverage for this project {project_name}
fetchAccessibilityIssues
Fetch accessibility issues from a completed scan with pagination support. Use cursor parameter to get subsequent pages of results.
fetchAutomationScreenshots
Fetch and process screenshots from a BrowserStack Automate session
fetchBuildInsights
Fetches insights about a BrowserStack build by combining build details and quality gate results.
fetchPercyChanges
Retrieves and summarizes all visual changes detected by Percy AI between the latest and previous builds, helping quickly review what has changed in your project.
fetchRCA
Fetch AI Root Cause Analysis for the current user's failed BrowserStack Automate/App-Automate tests. Suggests fixes only; never auto-apply, require explicit user approval.
fetchSelfHealedSelectors
Fetch BrowserStack self-healed selectors plus the test source code for the run. Provide exactly one of sessionId (single Automate / App-Automate session) or buildUuid (full self-healing report for a build). Pass the returned locator pairs to prepareSelfHealingPlan to plan edits.
getAccessibilityAuthConfig
Retrieve an existing authentication configuration by ID.
getBuildId
Get the BrowserStack build ID for a given project and build name, scoped to the current user's builds.
getFailureLogs
Fetch various types of logs from a BrowserStack session. Supports both automate and app-automate sessions.
getSubTestPlan
Fetch a sub-test-plan (STP-*) under a parent plan (TP-*). Returns metadata and linked test runs.
getTestPlan
Fetch a test plan by identifier (TP-*) from BrowserStack Test Management. Returns plan metadata, the full list of linked test runs, total test-case count across runs, and a status summary — suitable for generating test documentation or QA status reports.
listBuildId
Get the latest build ID for a project and build name, across all users (no user filter).
listFolders
List folders in a BrowserStack Test Management project, returning each folder's id and name (plus case counts and sub-folder counts). Pass parent_id to list sub-folders under a specific folder instead of top-level folders.
listSubTestPlans
List sub-test-plans under a parent test plan (TP-*) in a Test Management project. Supports pagination.
listTestCases
List test cases in a project, optionally scoped to a specific folder. Omit folder_id to list all test cases in the project; provide folder_id (discoverable via listFolders) to list only that folder's cases. Supports filters: case_type, priority, pagination.
listTestCaseTemplates
List test-case templates with their numeric template_id. Use the id with createTestCase to apply a custom template (the 'template' slug only selects system templates).
listTestFiles
Lists all test files for a given set of directories.
listTestIds
List test IDs from a BrowserStack Automate build, optionally filtered by status
listTestPlans
List test plans in a BrowserStack Test Management project. Returns each plan's identifier (TP-*), name, status, description, dates, and active/closed test-run counts. Supports pagination.
listTestRuns
List test runs in a project with optional filters (date ranges, assignee, state, etc.)
managePercyBuildApproval
Approve or reject a Percy build
percyVisualTestIntegrationAgent
Integrate Percy visual testing into new projects and demonstrate visual change detection through a step-by-step simulation. This tool handles initial Percy integration, setup, and creates a working demonstration for new users. Primary tool for prompts like: "Integrate percy for this project", "Integrate percy in this project {project_name}"
prepareSelfHealingPlan
Build a self-healing edit plan that bundles locator pairs with test source code for the calling LLM to apply with its own editing tools. This tool does NOT modify files — it returns structured context so the LLM can edit only the relevant call sites (avoids blind find/replace across shared ids/classes). sessions accepts the canonical shape [{sessionId, locators: [{original, healed, thought?}]}], a single session object, an envelope {sessions: [...]}, the raw report {healing_logs: [...]} (with healed_selectors aliasing locators), and snake_case keys (session_id, original_locator, healed_locator, healing_thought).
runAppLiveSession
Use this tool when user wants to manually check their app on a particular mobile device using BrowserStack's cloud infrastructure. Can be used to debug crashes, slow performance, etc.
runAppTestsOnBrowserStack
Execute pre-built native mobile test suites (Espresso for Android, XCUITest for iOS) by direct upload to BrowserStack. ONLY for compiled .apk/.ipa test files. This is NOT for SDK integration or Appium tests. For Appium-based testing with SDK setup, use 'setupBrowserStackAppAutomateTests' instead.
runBrowserLiveSession
Launch a BrowserStack Live session (desktop or mobile).
runPercyScan
Run a Percy visual test scan. Example prompts : Run this Percy build/scan. Never run percy scan/build without this tool
setupBrowserStackAppAutomateTests
Set up BrowserStack App Automate SDK integration for Appium-based mobile app testing. ONLY for Appium based framework . This tool configures SDK for various languages with appium. For pre-built Espresso or XCUITest test suites, use 'runAppTestsOnBrowserStack' instead.
setupBrowserStackAutomateTests
Set up and run automated web-based tests on BrowserStack using the BrowserStack SDK. Use this tool for functional or integration test setup on BrowserStack only. For any visual testing or Percy integration, use the dedicated Percy setup tool. Example prompts: run this test on browserstack; set up this project for browserstack.
startAccessibilityScan
Start an accessibility scan via BrowserStack and retrieve a local CSV report path.
takeAppScreenshot
Use this tool to take a screenshot of an app running on a BrowserStack device. This is useful for visual testing and debugging.
updateTestCase
Update an existing test case in BrowserStack Test Management. Any subset of the following fields may be changed: name, description, preconditions, test_case_steps, owner, priority, case_type, automation_status, status, tags, issues, custom_fields. Only the supplied fields are modified.
updateTestRun
Update a test run's metadata and/or add test cases to it.
uploadProductRequirementFile
Upload files (e.g., PDRs, PDFs) to BrowserStack Test Management and retrieve a file mapping ID. This is utilized for generating test cases from files and is part of the Test Case Generator AI Agent in BrowserStack.
BEFORE YOU INSTALL
What to know first
Tools you get
44 tools when we connected. Some tools, including createTestCasesFromFile, listTestFiles and runPercyScan, are not available on the hosted https://mcp.browserstack.com/mcp endpoint; the local npx install exposes all 44.
Requires
- npx on PATH
- BROWSERSTACK_USERNAME in your environment
- BROWSERSTACK_ACCESS_KEY in your environment
Where it runs
All 4 documented clients run the server on your machine.
CONTEXT COST
Heavy Standing cost
Rated by the size of the 44 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @browserstack/mcp-server@latestMCP Clients
VS Code
VS CODE · JSON
{
"servers": {
"browserstack": {
"command": "npx",
"args": [
"-y",
"@browserstack/mcp-server@latest"
],
"env": {
"BROWSERSTACK_USERNAME": "<YOUR_BROWSERSTACK_USERNAME>",
"BROWSERSTACK_ACCESS_KEY": "<YOUR_BROWSERSTACK_ACCESS_KEY>"
}
}
}
}Cursor, Claude Desktop, Cline
JSON
{
"mcpServers": {
"browserstack": {
"command": "npx",
"args": [
"-y",
"@browserstack/mcp-server@latest"
],
"env": {
"BROWSERSTACK_USERNAME": "<YOUR_BROWSERSTACK_USERNAME>",
"BROWSERSTACK_ACCESS_KEY": "<YOUR_BROWSERSTACK_ACCESS_KEY>"
}
}
}
}
