Log inSubmit server
MCP Server logo

MCP Server

by browserstack

Connects AI clients to BrowserStack for manual testing, automation, accessibility scans, test management, and test debugging.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server-105": {
      "command": "npx",
      "args": [
        "-y",
        "@browserstack/mcp-server@latest"
      ],
      "env": {
        "BROWSERSTACK_USERNAME": "YOUR_VALUE_HERE",
        "BROWSERSTACK_ACCESS_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 52 tools correctly (3d ago).

Overview

  • browserstack
  • browser-automation
  • testing
  • accessibility
  • test-management

The browserstack/mcp-server MCP server connects AI clients to BrowserStack's testing platform through natural-language prompts. It supports manual web and mobile testing, automated test execution and debugging, accessibility scans, test management, and BrowserStack AI agents. Reach for it when you want to operate BrowserStack from an IDE or other MCP-enabled client instead of switching between separate testing tools.

Use cases

  • Open local websites on remote browsers and devices
  • Run and debug Playwright, Selenium, and Jest tests
  • Scan websites for accessibility issues
  • Create test cases and runs in Test Management
  • Generate or repair tests with BrowserStack AI agents

Key features

  • Manual web testing across browsers and devices
  • Real-device mobile app testing
  • Automated test execution and failure analysis
  • Accessibility scanning for local and production sites
  • Test Management operations
  • BrowserStack AI agent access

Tools52

What MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~15.6k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

4/4 checks healthy over the last 40d

What it can do

From the 52 tools this server returned when we ran it; 51 declare their own safety hints.

Runs commands · 1Can delete or modify data · 3Writes files · 2Handles credentials · 2Makes network requests · 17Read-only tools · 46
Network at startup4 connections
Files written at startup1
Install scriptsNone
npm provenanceSigned build
Package age544 days
Maintainers1

Observed 2026-10-19 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @browserstack/mcp-server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars155Stargazers on the source repository.
npm downloads88kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed52Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Server works

What browserstack/mcp-server MCP server does

The browserstack/mcp-server MCP server exposes BrowserStack testing workflows to AI clients. It can open websites on selected browsers and devices, launch mobile apps on real devices, run automated tests, retrieve test information, and help investigate failures. It also supports BrowserStack Test Management operations such as creating projects, folders, test cases, and test runs, then updating results.

The server covers several BrowserStack product areas:

  • Manual web testing across browsers, operating systems, and devices, including sites running on localhost.
  • Manual mobile app testing on real devices and operating-system versions.
  • Automated testing with frameworks and tools including Playwright, Selenium, and Jest.
  • Accessibility scans for local or production websites.
  • Test Management and BrowserStack AI agents for test generation, low-code automation, and self-healing assistance.

How it works

Prompts are sent from an MCP-enabled IDE, LLM application, or agent workflow. The server translates those requests into actions on the BrowserStack Test Platform. Example requests include opening a local site in Edge, running a test suite on BrowserStack infrastructure, scanning a production site for accessibility issues, or creating a test run from selected test cases.

For automated-test failures, the server can fetch logs, analyze failures, identify likely causes, and suggest fixes. Root Cause Analysis results are proposals only: the server does not edit files automatically. The assistant must show the suggestion and receive approval before changing code.

The hosted endpoint at mcp.browserstack.com uses stateless Streamable HTTP.

Setup and configuration

The browserstack/mcp-server MCP server requires Node.js 20.9 or later. Node.js 22.15.0 LTS is recommended by the project. Check the installed version with node --version before setup.

BrowserStack account access is also required. Create an account and obtain the account username and access key from BrowserStack account settings. The project provides one-click setup links for VS Code and Cursor, and also supports alternate MCP configuration methods through the package and server configuration.

The hosted Streamable HTTP option is available at mcp.browserstack.com. A local setup may require the BrowserStack account credentials and a compatible Node.js runtime.

Tools and capabilities

The browserstack/mcp-server MCP server supports:

  • Opening websites on requested browser, device, and operating-system combinations.
  • Opening mobile apps on specified real devices and investigating crashes.
  • Running and porting automated test suites on BrowserStack infrastructure.
  • Reviewing test logs and using Test Observability data to investigate failures.
  • Scanning local or public websites for accessibility issues and identifying fixes.
  • Creating and organizing Test Management projects, folders, cases, and runs.
  • Listing test cases by criteria such as priority and updating test results.
  • Accessing BrowserStack AI agents for PRD-based test generation, low-code automation, and flaky-test assistance.

Limitations and notes

BrowserStack plan access and account credentials are prerequisites for using the platform.

The server does not automatically apply code changes suggested by Root Cause Analysis. Any proposed edit requires explicit approval from the user or assistant workflow. Local testing also depends on the target application being reachable, while BrowserStack account and plan permissions determine which platform features can be used.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Server

browserstack/mcp-server is an MCP server that connects AI clients to BrowserStack's Test Platform. Its main tools support manual web and mobile testing, automated test execution and debugging, accessibility scans, Test Management operations, and BrowserStack AI agents. It accepts natural-language requests from MCP-enabled IDEs and applications.

Install it through the provided one-click setup for VS Code or Cursor, or configure it through another MCP client using the package and server settings. Node.js 20.9 or newer is required, and a BrowserStack account with username and access key is needed.

Yes, browserstack/mcp-server works with Cursor. The README provides a one-click Cursor setup option, and the hosted Streamable HTTP server can be used by Cursor without a configuration change.

No, it does not apply code changes automatically. It can inspect failures, retrieve logs, identify likely causes, and return a suggested fix, but the assistant must present the proposal and receive explicit approval before editing files.

Node.js 20.9 or newer is required. The project recommends Node.js 22.15.0 LTS and suggests checking the installed version with `node --version`.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-server-105?style=directory)](https://allmcps.com/mcp/mcp-server-105)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-server-105"><img src="https://allmcps.com/api/badge/mcp-server-105?style=directory" alt="MCP Server on AllMCPs" /></a>