BrowserStack MCP Server

Descriptor

Candidate descriptor · transport

Tools

• createProjectOrFolder — Create a Test Management project and/or folders to organize test cases. Returns with Folder ID, Project ID and Test Management Link to access the TM Project Dashboard.
• createTestCase — Add a manual test case under a specific project/folder (uses project identifier like PR-xxxxx and a folder ID).
• updateTestCase — Update an existing test case. Any subset of fields may be changed (name, priority, status, steps, tags, etc.); only supplied fields are modified.
• listTestCases — List test cases for a project, optionally scoped to a folder (supports filters like case_type, priority, and pagination).
• listFolders — List folders in a Test Management project (returns each folder's id, name, case counts, and sub-folder counts). Pass a parent_id to list sub-folders.
• listTestCaseTemplates — List test-case templates with their numeric template_id, for use with createTestCase to apply a custom template.
• createTestRun — Create a test run (suite) for selected test cases in a project.
• listTestRuns — List test runs for a project (filter by dates, assignee, state).
• updateTestRun — Update a test run's name/state and/or add test cases to it.
• addTestResult — Add a manual execution result (passed/failed/blocked/skipped) for a test case within a run.
• createTestCasesFromFile — Generate test cases in bulk from an uploaded file using the Test Case Generator AI Agent.
• listTestPlans — List test plans (TP-*) in a project, with name, status, dates, and active/closed run counts. Supports pagination.
• getTestPlan — Fetch a test plan by identifier (TP-*) with its metadata, linked test runs, total test-case count, and status summary.
• listSubTestPlans — List sub-test-plans (STP-*) under a parent test plan (TP-*). Supports pagination.
• getSubTestPlan — Fetch a sub-test-plan (STP-*) under a parent plan, with its metadata and linked test runs.
• setupBrowserStackAutomateTests — Integrate BrowserStack SDK and run web tests on BrowserStack. For visual testing/Percy, use the dedicated Percy tools.
• fetchAutomationScreenshots — Fetch screenshots captured during a given Automate/App Automate session.
• getFailureLogs — Retrieve error logs for Automate/App Automate sessions (optionally by Build ID for App Automate).
• fetchBuildInsights — Fetch insights about a BrowserStack build by combining build details and quality-gate results.
• runAppLiveSession — Start a manual app testing session on a real device in the cloud.
• runBrowserLiveSession — Start a Live session for website testing on desktop or mobile browsers.
• takeAppScreenshot — Launch the app on a specified device and capture a quick verification screenshot to confirm your app has launched.
• runAppTestsOnBrowserStack — Run pre-built native mobile test suites (Espresso/XCUITest) by direct upload of compiled .apk/.ipa test files.
• setupBrowserStackAppAutomateTests — Set up BrowserStack App Automate SDK integration for Appium-based mobile app testing.
• accessibilityExpert — Ask the A11y Expert (WCAG 2.0/2.1/2.2, mobile/web usability, best practices).
• startAccessibilityScan — Start a web accessibility scan and retrieve a local CSV report path.
• createAccessibilityAuthConfig — Create an authentication configuration (form-based or basic) for accessibility scans behind a login.
• getAccessibilityAuthConfig — Retrieve an existing accessibility authentication configuration by ID.
• fetchAccessibilityIssues — Fetch accessibility issues from a completed scan, with pagination support.
• percyVisualTestIntegrationAgent — Integrate Percy visual testing into a new project and demonstrate visual change detection with a step-by-step simulation.
• expandPercyVisualTesting — Set up or expand Percy visual testing coverage for existing projects (Percy Web Standalone and Percy Automate).
• addPercySnapshotCommands — Add Percy snapshot commands to the specified test files.
• listTestFiles — List all test files for a given set of directories.
• runPercyScan — Run a Percy visual test scan.
• fetchPercyChanges — Retrieve and summarize visual changes detected by Percy AI between the latest and previous builds.
• managePercyBuildApproval — Approve or reject a Percy build.
• uploadProductRequirementFile — Upload a PRD/screenshot/PDF and get a file mapping ID (used with createTestCasesFromFile).
• createLCASteps — Generate Low Code Automation (LCA) steps from a manual test case in Test Management.
• fetchSelfHealedSelectors — Retrieve AI self-healed selectors (plus test source) to fix flaky tests caused by DOM changes.
• prepareSelfHealingPlan — Build a self-healing edit plan that bundles locator pairs with test source for your LLM to apply. Does NOT modify files itself.
• fetchRCA — Fetch AI Root Cause Analysis for your failed Automate/App-Automate tests (by numeric test ID). Suggests fixes only; never auto-applies.
• getBuildId — Get the BrowserStack build ID for a given project and build name, scoped to your builds.
• listBuildId — Get the latest build ID for a project and build name, across all users (no user filter).
• listTestIds — List test IDs from a BrowserStack Automate build, filtered by status (passed/failed/pending/skipped).

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

curl "https://apis.io/api/v1/mcp/browserstack-mcp-server"

curl "https://apis.io/api/v1/mcp?limit=25"