BrowserStack MCP Server

Comprehensive Test Platform

Manage test cases, execute manual or automated tests, debug issues, and even fix code—directly within tools like Cursor, Claude, or any MCP-enabled client, using plain English.

Test from anywhere:

Easily connect the BrowserStack Test Platform to your favourite AI tools, such as IDEs, LLMs, or agentic workflows.

Test with natural language:

Manage, execute, debug tests, and even fix code using plain English prompts.

Reduced context switching:

Stay in flow—keep all project context in one place and trigger actions directly from your IDE or LLM.

⚡️ One Click MCP Setup

Click on the buttons below to install MCP in your respective IDE:

Note: The hosted Remote MCP server (mcp.browserstack.com) is now fully stateless over Streamable HTTP — any Streamable-HTTP client (Claude, Cursor, VS Code, ChatGPT) connects with no configuration change.

Note : Ensure you are using Node version >= `20.9`

Check your node version using node --version. Recommended version: v22.15.0 (LTS)
To Upgrade Node :
1. On macOS (Homebrew) - brew update && brew upgrade node or if using (nvm) - nvm install 22.15.0 && nvm use 22.15.0 && nvm alias default 22.15.0
1. On Windows (nvm-windows) : nvm install 22.15.0 && nvm use 22.15.0
👉 Or directly download the Node.js LTS Installer

.

💡 Usage Examples

📱 Manual App Testing

Test mobile apps on real devices across the latest OS versions. Reproduce bugs and debug crashes without setup hassles. Below are some sample prompts to use your mobile apps on BrowserStack's extensive cloud of real devices

# Open app on specific device
"open my app on a iPhone 15 Pro Max"

# Debug app crashes
"My app crashed on Android 14 device, can you help me debug?"

Unlike emulators, test your app's real-world performance on actual devices. With advanced App-Profiling features, you can debug crashes and performance issues in real-time.
Access all major devices and OS versions from our device grid, We have strict SLAs to provision our global datacenters with newly released devices on launch day.

🌐 Manual Web Testing

Similar to the app testing, you can use the following prompts to test your websites on BrowserStack's extensive cloud of real browsers and devices. Don't have Edge browser installed on your machine ? We've got you covered!

# Test your websites
"open my website hosted on localhost:3001 on Edge"
"open browserstack.com on latest version of Chrome"

Test websites across different browsers and devices. We support every major browser across every major OS.
Seamlessly test websites hosted locally on your machine, no need to deploy to a remote server!

🧪 Automated Testing (Playwright, Selenium, A11y and more..)

Auto-analyze, diagnose, and even fix broken test scripts right in your IDE or LLM. Instantly fetch logs, identify root causes, and apply context-aware fixes. No more debugging loops. Below are few example prompts to run/debug/fix your automated tests on BrowserStack's Test Platform.

Note: When fetching Root Cause Analysis (RCA) for a test, the server returns the suggested fix as a proposal only. It never applies code changes automatically — your assistant must present the suggestion and wait for your explicit approval before editing any files.

#Port test suite to BrowserStack
"Setup test suite to run on BrowserStack infra"

#Run tests on BrowserStack
“Run my tests on BrowserStack”

#AI powered debugging of test failures
"My App Automate tests have failed, can you help me fix the new failures?"

Fix test failures reported by your CI/CD pipeline by utilising our industry leading Test Observability features. Find more info here.
Run tests written in Jest, Playwright, Selenium, and more on BrowserStack's Test Platform

🌐 Accessibility

Catch accessibility issues early with automated, local a11y scans. Get one-click, AI-suggested fixes. No docs hunting, no CI surprises. Ensure WCAG and ADA compliance with our Accessibility Testing tool

#Scan accessibility issues while development
"Scan & help fix accessibility issues for my website running locally on localhost:3000"

#Scan accessibility issues on production site
“Run accessibility scan & identify issues on my website - www.bstackdemo.com”

📋 Test Management

Create and manage test cases, create test plans and trigger test runs using natural language. Below are a few example prompts to utilise capabilities of BrowserStack's Test Management with MCP server.

# Create project & folder structure
"create new Test management project named My Demo Project with two sub folders - Login & Checkout"

# Add test cases
"add invalid login test case in Test Management project named My Demo Project"

# List added test cases 
"list high priority Login test cases from Test Management project - My Demo Project"

# Create test run
"create a test run for Login tests from Test Management project - My Demo Project"

# Update test results
"update test results as passed for Login tests test run from My Demo Project"

⚡ Load Testing

Run and analyse load tests at scale without leaving your IDE or chat — find tests, start and stop runs, read reports and AI Insights, compare runs, and check your VU-hours. Works with API (JMeter, k6, Gatling, Locust), browser (Playwright, Selenium, WebdriverIO, Nightwatch) and hybrid load tests on BrowserStack's Load Testing. These go through the core tools.

# Find a test
"find my load test called checkout-api"

# Run it
"run checkout-api for 5 minutes with 100 virtual users"

# Check on it
"is my checkout-api run finished yet?"

# Read the results
"what was the p95 response time and error rate of the last checkout-api run?"

# Compare two runs of the same test
"did the latest checkout-api run regress compared with the previous one?"

# Check quota before a big run
"how many VU-hours do I have left, and what would a 30-minute run with 500 VUs cost?"

🧪 Access BrowserStack AI agents

Generate test cases from PRDs, convert manual tests to low-code automation, and auto-heal flaky scripts powered by BrowserStack’s AI agents, seamlessly integrated into your workflow. Below are few example prompts to access Browserstack AI agents

#Test case generator agent
"With Browserstack AI, create relevant test cases for my PRD located at /usr/file/location"


#Low code authoring agent
“With Browserstack AI, automate my manual test case X, added in Test Management”


#Self healing agent
“Help fix flaky tests in my test script with Browserstack AI self healing”

🛠️ Installation

📋 Prerequisites for MCP Setup

Node.js version >= 20.9 (see the note under One Click MCP Setup above).
A BrowserStack account (steps below).

To install with one click, use the Install in VS Code / Install in Cursor buttons under One Click MCP Setup at the top of this page.

Alternate ways to Setup MCP server

Create a BrowserStack Account
- Sign up for BrowserStack if you don't have an account already.
- ℹ️ If you have an open-source project, we'll be able to provide you with a free plan.
- Once you have an account (and purchased appropriate plan), note down your username and access_key from Account Settings.
Install the MCP Server
- VSCode (Copilot - Agent Mode): .vscode/mcp.json:
  - Locate or Create the Configuration File: In the root directory of your project, look for a folder named .vscode. This folder is usually hidden so you will need to find it as mentioned in the expand.
  - If this folder doesn't exist, create it.
  - Inside the .vscode folder, create a new file named mcp.json
  - Add the Configuration: Open the mcp.json file and then add the following JSON content.
  - Replace the username and <access_key> with your BrowserStack credentials.
```
{
  "servers": {
    "browserstack": {
      "command": "npx",
      "args": ["-y", "@browserstack/mcp-server@latest"],
      "env": {
        "BROWSERSTACK_USERNAME": "<username>",
        "BROWSERSTACK_ACCESS_KEY": "<access_key>"
      }
    }
  }
}
```
- In VSCode, make sure to click on Start button in the MCP Server to start the server.
** Alternate way to setup MCP on VSCode Copilot

1.Click on the gear icon to Select Tools

2. A tool menu would appear at the top-centre, scroll down on the menu at the top and then Click on Add MCP Server

3. Select NPM package option (Install fron an NPM package) - 3rd in the list

4. Enter NPM Package Name (@browserstack/mcp-server)

5. Enter browserstack user name and access key
- For Cursor: .cursor/mcp.json:
```
{
  "mcpServers": {
    "browserstack": {
      "command": "npx",
      "args": ["-y", "@browserstack/mcp-server@latest"],
      "env": {
        "BROWSERSTACK_USERNAME": "<username>",
        "BROWSERSTACK_ACCESS_KEY": "<access_key>"
      }
    }
  }
}
```
- For Claude Desktop: ~/claude_desktop_config.json:
```
{
  "mcpServers": {
    "browserstack": {
      "command": "npx",
      "args": ["-y", "@browserstack/mcp-server@latest"],
      "env": {
        "BROWSERSTACK_USERNAME": "<username>",
        "BROWSERSTACK_ACCESS_KEY": "<access_key>"
      }
    }
  }
}
```
- For Cline

Click the “MCP Servers” icon in the navigation bar Select the “Installed” tab. Click the “Configure MCP Servers” button at the bottom of the pane.

{
  "mcpServers": {
    "browserstack": {
      "command": "npx",
      "args": ["-y", "@browserstack/mcp-server@latest"],
      "env": {
        "BROWSERSTACK_USERNAME": "<username>",
        "BROWSERSTACK_ACCESS_KEY": "<access_key>"
      }
    }
  }
}

🧭 Core Tools

Five core tools let your AI assistant find and run any BrowserStack workflow. Your assistant loads every tool an MCP server exposes at the start of each session, so one tool per workflow would fill your context window and slow down the whole session. Instead, your assistant uses the core tools to search a catalog of BrowserStack tools in plain language and run the one it needs.

Tool	Description
`listProducts`	Lists the BrowserStack products in the catalog, with a short summary of what each product covers
`describeEntity`	Explains one entity: its aliases, ID format, parent and related entities, and the capabilities that act on it
`searchCapability`	Finds the capabilities that match a plain-language request, with everything your assistant needs to run each one
`describeCapability`	Returns the full details of one capability, such as its parameters, request body and response format
`invokeCapability`	Runs one capability and returns the product's response unchanged. Changes to data need your approval

See Core tools for parameters and how changes to data are approved.

All tools — See docs/TOOLS.md for every tool organised by product, or BrowserStack MCP tools & workflows for product workflows.

File & app uploads: tools that upload a local file/app (uploadProductRequirementFile, takeAppScreenshot, runAppTestsOnBrowserStack, runAppLiveSession) require the MCP_UPLOAD_BASE_DIR env var set to a directory containing those files; uploads are restricted to it.

🚀 Remote MCP Server

Remote MCP comes with all the functionalities of an MCP server without the hassles of complex setup or local installation.

Key benefits:

✅ Works seamlessly in enterprise networks without worrying about firewalls or binaries or where local installation is not allowed.
✅ Secure OAuth integration – no password sharing or manual credential handling.

Limitations:

❌ No Local Testing support (cannot test apps behind VPNs, firewalls, or localhost). If you have to do Local Testing, you would have to use a BrowserStack Local MCP server.
❌ Latency can be slightly higher, but nothing considerable — you generally won’t notice it in normal use.

Installation Steps:

On VSCode (Copilot - Agent Mode): .vscode/mcp.json:
- Locate or Create the Configuration File:
- In the root directory of your project, look for a folder named .vscode. This folder is usually hidden so you will need to find it as mentioned in the expand.
- If this folder doesn't exist, create it.
- Inside the .vscode folder, create a new file named mcp.json
- To setup Remote BrowserStack MCP instead of local BrowserStack MCP you can add the following JSON content :
  
  Alternative way to Setup Remote MCP
- Step 1.Click on the gear icon to Select Tools
- Step 2. A tool menu would appear at the top-centre, scroll down on the menu at the top and then Click on Add MCP Server
- Step 3. Click on HTTP option
- Step 4. Paste Remote MCP Server URL : https://mcp.browserstack.com/mcp
- Step 5. Give server id as : browserstack
- Step 6. In VSCode Click on start MCP Server and then click on "Allow"

⚠️ Important Notes

The BrowserStack MCP Server is under active development and currently supports a subset of the MCP spec. More features will be added soon.
Tool invocations rely on the MCP Client which in turn relies on an LLM, hence there can be some non-deterministic behaviour that can lead to unexpected results. If you have any suggestions or feedback, please open an issue to discuss.

📝 Contributing

We welcome contributions! Please open an issue to discuss any changes you'd like to make. 👉 Click here to view our Contributing Guidelines

📞 Support

For support, please:

Open an issue in our GitHub repository if you face any issues related to the MCP Server.
Contact our support team for any other queries.

🚀 More Features Coming Soon

Stay tuned for exciting updates! Have any suggestions? Please open an issue to discuss.

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
assets		assets
capability		capability
docs		docs
scripts		scripts
src		src
tests		tests
.env.example		.env.example
.gitignore		.gitignore
.nvmrc		.nvmrc
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
eslint.config.mjs		eslint.config.mjs
glama.json		glama.json
llms-install.md		llms-install.md
package-lock.json		package-lock.json
package.json		package.json
server.json		server.json
tsconfig.json		tsconfig.json
vite.config.ts		vite.config.ts

Navigation Menu

Repository navigation

About

Repository files navigation

BrowserStack MCP Server

Test from anywhere:

Test with natural language:

Reduced context switching:

⚡️ One Click MCP Setup

Note : Ensure you are using Node version >= `20.9`

💡 Usage Examples

📱 Manual App Testing

🌐 Manual Web Testing

🧪 Automated Testing (Playwright, Selenium, A11y and more..)

🌐 Accessibility

📋 Test Management

⚡ Load Testing

🧪 Access BrowserStack AI agents

🛠️ Installation

📋 Prerequisites for MCP Setup

Alternate ways to Setup MCP server

** Alternate way to setup MCP on VSCode Copilot

🧭 Core Tools

🚀 Remote MCP Server

Key benefits:

Limitations:

Installation Steps:

Alternative way to Setup Remote MCP

⚠️ Important Notes

📝 Contributing

📞 Support

🚀 More Features Coming Soon

About

Releases

Used by

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

BrowserStack MCP Server

Test from anywhere:

Test with natural language:

Reduced context switching:

⚡️ One Click MCP Setup

Note : Ensure you are using Node version >= 20.9

💡 Usage Examples

📱 Manual App Testing

🌐 Manual Web Testing

🧪 Automated Testing (Playwright, Selenium, A11y and more..)

🌐 Accessibility

📋 Test Management

⚡ Load Testing

🧪 Access BrowserStack AI agents

🛠️ Installation

📋 Prerequisites for MCP Setup

Alternate ways to Setup MCP server

** Alternate way to setup MCP on VSCode Copilot

🧭 Core Tools

🚀 Remote MCP Server

Key benefits:

Limitations:

Installation Steps:

Alternative way to Setup Remote MCP

⚠️ Important Notes

📝 Contributing

📞 Support

🚀 More Features Coming Soon

About

Topics

Resources

Contributing

Stars

Watchers

Forks

Releases

Used by

Contributors

Languages

Note : Ensure you are using Node version >= `20.9`