What it does

The server integrates BrowserStack's testing platform directly into Claude, VS Code, Cursor, and other MCP clients. With 39 tools, it covers manual testing on real devices and browsers, automated test execution and debugging (Playwright, Selenium, Jest), accessibility scanning, and test management. Launch an app on an iPhone 15, debug a failed test, or scan your localhost for WCAG compliance—all via plain-English prompts. This eliminates context switching between your IDE and BrowserStack's web interface.

Who it's for

QA engineers and test automation specialists who want to manage and run tests across real mobile devices and browsers without leaving their IDE. Mobile testers reproducing device-specific bugs, accessibility compliance auditors, and CI/CD engineers integrating test debugging into deployment pipelines.

Common use cases

Test mobile apps on real iOS/Android devices instead of emulators, catching real-world performance and OS-version-specific bugs
Debug failing Playwright or Selenium tests with AI-powered diagnostics and suggested fixes
Run cross-browser web tests on localhost without deploying to a remote server
Scan production or local websites for accessibility issues (WCAG, ADA compliance)
Create, organize, and execute test cases using natural language prompts

Setup pitfalls

Node version must be ≥18.0 (v22.15.0 LTS recommended); check with node --version
CI is currently failing—review recent commits and status before use
Requires BrowserStack account and valid API credentials configured in your environment
Filesystem write access needed to store test logs and result files

Tool name

Description

Destructive?

getFailureLogs

✓ no

accessibilityExpert

✓ no

startAccessibilityScan

✓ no

createAccessibilityAuthConfig

✓ no

getAccessibilityAuthConfig

✓ no

fetchAccessibilityIssues		✓ no
setupBrowserStackAutomateTests		✓ no
fetchBuildInsights		✓ no
fetchRCA		✓ no
getBuildId		✓ no
listTestIds		✓ no
fetchAutomationScreenshots		✓ no
runAppLiveSession⚠		⚠ yes
getFailuresInLastRun⚠		⚠ yes
percyVisualTestIntegrationAgent		✓ no
expandPercyVisualTesting		✓ no
addPercySnapshotCommands		✓ no
listTestFiles		✓ no
runPercyScan⚠		⚠ yes
fetchPercyChanges		✓ no
managePercyBuildApproval		✓ no
runBrowserLiveSession⚠		⚠ yes
takeAppScreenshot		✓ no
runAppTestsOnBrowserStack⚠		⚠ yes
setupBrowserStackAppAutomateTests		✓ no
fetchSelfHealedSelectors		✓ no
prepareSelfHealingPlan		✓ no
createProjectOrFolder		✓ no
createTestCase		✓ no
updateTestCase		✓ no
listTestCases		✓ no
listFolders		✓ no
createTestRun⚠		⚠ yes
listTestRuns⚠		⚠ yes
updateTestRun⚠		⚠ yes
addTestResult		✓ no
uploadProductRequirementFile		✓ no
createTestCasesFromFile		✓ no
createLCASteps		✓ no
listTestPlans		✓ no
getTestPlan		✓ no
listSubTestPlans		✓ no
getSubTestPlan		✓ no

@browserstack/mcp-server

What it does

Who it's for

Common use cases

Setup pitfalls