BrowserStack MCP Server

One Platform For All Your Testing Needs

Enable every developer and tester in your team, whether they are testing manually, starting their automation journey, or scaling test automation. BrowserStack MCP Server allows you to use our cutting-edge Test Platform directly from your favourite AI tools.

Why BrowserStack ?

💡 Usage Examples

📱 Manual App Testing

Use the following prompts to use your mobile apps on BrowserStack's extensive cloud of real devices. Stop using emulators!

# 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 local websites
"open my website hosted on localhost:3001 on Edge"

• 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..)

Use the following prompts to run/debug/fix your automated tests on BrowserStack's Test Platform.

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

# Debug test failures
"My test suite failed, can you help me fix the new failures?"

# Accessibility testing
"check for accessibility issues on my www.mywebsite.com"

• 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 Testing: Ensure WCAG and ADA compliance with our Accessibility Testing tool

🛠️ Installation

1. Create a BrowserStack Account

   • # 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.

2. Install the MCP Server

   • VSCode (Copilot - Agent Mode): .vscode/mcp.json:

   {
     "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.
   • For Cursor: .cursor/mcp.json:

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

   • 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>"
         }
       }
     }
   }

🤝 Recommended MCP Clients

• We recommend using Github Copilot or Cursor for automated testing + debugging use cases.
• For manual testing use cases (Live Testing), we recommend using Claude Desktop.

⚠️ 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.

📞 Support

For support, please:

• Check our documentation
• 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.

🔗 Resources

• BrowserStack Test Platform
• MCP Protocol Documentation
• Device Grid
• Accessibility Testing