Sold by: BrowserStack
Deployed on AWS
AWS Free Tier
Connect your favorite AI tools like GitHub Copilot, Claude, and Cursor directly to BrowserStack end-to-end testing stack, all from within your IDE. BrowserStack MCP Server is a secure, open-source bridge that enables natural language test management, execution, debugging, and accessibility scans seamlessly.
4.4
Overview
BrowserStack MCP Server
BrowserStack MCP Server transforms modern developer workflows by enabling powerful, real-time interaction between your IDE AI assistants and the full BrowserStack Test Platform.
This MCP Server requires customers to have an active subscription to BrowserStack:
View on AWS Marketplace
Developers install the MCP Server locally to securely connect tools like GitHub Copilot, Claude, or Cursor and instantly, all from a single interface and by using natural language prompts:
- Perform live device/browser tests
- Run and manage test cases
- Trigger automation suites
- Scan for accessibility
- Debug failures
Key Capabilities
- Manual & Automated Web/App Testing: Live real device/browser sessions
- Test Management: Create, update, execute test cases and runs
- Debugging: Fetch and analyze logs, diagnose failures, recommend AI-powered fixes
- Accessibility Scanning: Detect and suggest fixes for A11y violations
- AI Agent-Driven Workflows: Generate and heal test cases, automate diagnostics
Highlights
- Seamless AI-Driven Test Management Orchestrate complete test workflows directly from your IDE or AI tool. Create, execute, debug, and update test cases with natural language in real time
- Instant Live & Automated Testing from Your Workflow Launch real device/browser sessions, run automation suites, and fetch results no dashboards or manual setup required. All actions stay in your local flow, minimizing distractions
- Security & Privacy First Credentials and test data are protected; nothing is stored or shared externally. MCP Server uses a secure, real-time protocol with data isolation across environments, ensuring compliance and peace of mind for enterprise teams
Details
Sold by
Categories
Delivery method
Integration protocol
Type
Deployed on AWS
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
This product is available free of charge. Free subscriptions have no end date and may be canceled any time.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Vendor refund policy
No refund
Custom pricing options
Request a private offer to receive a custom quote.
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
API-Based Agents & Tools
API-Based Agents and Tools integrate through standard web protocols. Your applications can make API calls to access agent capabilities and receive responses.
Additional details
Usage instructions
Getting Started with BrowserStack MCP Server
To get started using the remove MCP server, follow the instructions below:
Available Tools
This MCP server supports the following tools:
Test Management
- createProjectOrFolder — Create TM project/folder
- createTestCase — Add manual test case
- listTestCases — List test cases
- createTestRun — Create test run
- listTestRuns — List test runs
- updateTestRun — Update test run
- addTestResult — Add execution result
- createTestCasesFromFile — Bulk-create from file
Automate / SDK
- setupBrowserStackAutomateTests — Run tests with SDK
- fetchAutomationScreenshots — Fetch Automate screenshots
Observability
- getFailureLogs — Retrieve error logs
App Live
- runAppLiveSession — Start app testing session
Live
- runBrowserLiveSession — Start browser testing session
App Automate
- takeAppScreenshot — Capture quick app screenshot
- runAppTestsOnBrowserStack — Run automated mobile tests
Accessibility
- accessibilityExpert — WCAG/A11y expert Q&A
- startAccessibilityScan — Run accessibility scan
AI Agents
- fetchSelfHealedSelectors — AI self-healed selectors
- createLCASteps — Generate Low Code Automation steps
- uploadProductRequirementFile — Upload PRD/file for test generation
Prerequisites
- Install Node.js and npm
- Create a BrowserStack account: Sign up
- Get your BrowserStack Access Key from Account Settings
Authentication
Replace YOUR_BROWSERSTACK_KEY with your actual BrowserStack key below.
Claude Desktop
Edit the configuration file at:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
Add the below code:
{ "mcpServers": { "browserstack": { "command": "npx", "args": ["-y", "@browserstack/mcp-server@latest"], "env": { "BROWSERSTACK_USERNAME": "<username>", "BROWSERSTACK_ACCESS_KEY": "<access_key>" } } } }Cline
Cline stores MCP server configurations in a JSON file that can be modified.
In the Installed tab, click Configure MCP Servers to access the settings file.
Add the following:
{ "mcpServers": { "browserstack": { "command": "npx", "args": ["-y", "@browserstack/mcp-server@latest"], "env": { "BROWSERSTACK_USERNAME": "<username>", "BROWSERSTACK_ACCESS_KEY": "<access_key>" } } } } **Learn More** MCP Docs: <https://github.com/browserstack/mcp-server?tab=readme-ov-file>Resources
Vendor resources
Support
Vendor support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
BrowserStack is a software testing platform powering over two million daily tests across 19 global data centers. It provides developers and QAs with access to a cloud platform that allows them to test their websites and mobile applications across 3,500+ real mobile devices and browsers, replacing the need for teams to own and manage a complex in-house test infrastructure. BrowserStack helps Tesco, Shell, NVIDIA, Discovery, Wells Fargo, and over 50,000 customers deliver quality software at speed.
Make sure your Spryker commerce platform runs at peak performance on AWS and remains secure. Nagarro’s support and platform management capabilities guarantee optimal performance and security for your e-commerce operations.
Customer reviews
Rahul M.
BrowserStack Makes Cross-Browser and Real-Device Testing for .NET & Angular Effortless
Reviewed on May 30, 2026
Review provided by G2
What do you like best about the product?
Building full stack applications with .NET core and Angular means you own both ends of the stack - and when something breaks in production it could be anywhere. BrowserStack narrowed that search dramatically. Angular components consuming web APIs behaved completely differently across real browsers and I would never have caught that locally.
Third party API integrations that rendered response data inside the frontend showed inconsistencies on real mobile devices that no amount of local Chrome testing revealed. What genuinely impressed me was the tunnel feature connecting my locally running ASP.NET application directly to real remote devices - validating the complete request response cycle on actual hardware without deploying to a staging environment first saved significant time during active development cycles.
Third party API integrations that rendered response data inside the frontend showed inconsistencies on real mobile devices that no amount of local Chrome testing revealed. What genuinely impressed me was the tunnel feature connecting my locally running ASP.NET application directly to real remote devices - validating the complete request response cycle on actual hardware without deploying to a staging environment first saved significant time during active development cycles.
What do you dislike about the product?
SQL heavy operations returning large response payloads through Web APIs sometimes exposed session performance issues that made it unclear whether the slowness was application side or BrowserStack side. That ambiguity wastes debugging time when you are trying to isolate a genuine performance problem.
What problems is the product solving and how is that benefiting you?
Third party API response rendering inconsistencies across browsers was a recurring problem that reached clients before it reached us. BrowserStack flipped that timeline completely. C# backend returning perfectly structured JSON that Angular parsed and displayed differently on Safari versus Chrome versus real Android browsers - that category of bug used to generate client escalations regularly.
Now it gets caught during development before anyone outside the team sees it. ASP.NET Core application behavior validated across real device and browser combinations before every release means deployments became predictable rather than anxious. The team stopped firefighting post release and started shipping with genuine confidence backed by actual evidence.
Now it gets caught during development before anyone outside the team sees it. ASP.NET Core application behavior validated across real device and browser combinations before every release means deployments became predictable rather than anxious. The team stopped firefighting post release and started shipping with genuine confidence backed by actual evidence.
Sammy I.
Straightforward Real-Device Testing to Spot Rendering Discrepancies Fast
Reviewed on May 30, 2026
Review provided by G2
What do you like best about the product?
As a developer who’s heavily focused on backend logic, checking frontend layouts across native environments used to feel like a secondary chore. This platform makes it straightforward to review how things actually render on real devices and quickly spot any discrepancies.
What do you dislike about the product?
The only notable downside is that certain legacy browser variants or older operating system versions are sometimes missing from the lineup. That can make it a bit limiting to test retro layouts for older client applications when you specifically need an archaic environment for compatibility verification.
What problems is the product solving and how is that benefiting you?
It takes the guesswork and risk out of client-facing web deployments across Safari, Chrome, and a range of mobile environments. By replacing physical device setups with an on-demand testing cloud, it makes cross-browser and mobile validation much easier and more reliable.
Vasu R.
Nobody argued about browsers bugs anymore - BrowserStack made sure of that
Reviewed on May 30, 2026
Review provided by G2
What do you like best about the product?
What nobody tells you about BrowserStack is how much it changes the conversation inside the team. Before - browser compatibility discussion were full of assumptions, estimates and optimistic guesses. After - those conversations became short because anyone could verify anything in minutes. That cultural shift happened quietly but its impact on how the team communicates and makes decisions was surprisingly significant. Beyond that shift the platform itself delivers what it promises - real devices, reliable sessions, clean integration with existing pipelines, and honest results that local environments consistently fail to provide.
What do you dislike about the product?
When a CI pipeline fails because of a BrowserStack related issue during a critical release window, response times that feel acceptable during normal circumstances suddenly feel completely inadequate. The platform has earned enough trust to carry genuine business dependency - the support infrastructure needs to reflect that level of dependency rather than treating urgent issues with the same priority as routine questions.
What problems is the product solving and how is that benefiting you?
It solved a trust problem more than a technical problem. Stakeholders stopped questioning whether browser compatibility had been properly validated because the answer stopped being a confident guess and started being a verifiable fact. That shift in how quality gets communicated upward changed how delivery discussions happen at every level. Practically speaking - device specific bugs reaching production became rare rather than routine, QA cycles shortened because real device validation became faster and more systematic, and the team developed a shared language around browser testing that simply did not exist before BrowserStack became part of the workflow.
Aatish P.
Designed it beautifully - BrowserStack showed me what users actually saw
Reviewed on May 30, 2026
Review provided by G2
What do you like best about the product?
As someone who cares deeply about how things look and feel, nothing is more frustrating than a design that looks perfect in Figma but falls apart on a real device. BrowserStack fixed that gap completely. Seeing actual pixel rendering on real screens across different devices is something no design tool or browser preview can honestly replicate. Motion interactions that look smooth in prototypes sometimes stutter on real mobile hardware - BrowserStack surfaces that immediately. Game UI layouts that feel balanced on desktop look completely different on smaller Android screens and catching that before handoff saves everyone time and rework.
What do you dislike about the product?
The interface itself ironically could use better design thinking. Finding what you need quickly is not as intuitive as it should be for someone who values clean user experiences. Session timeouts also interrupt visual review flows at the worst moments - when you are carefully comparing design details across multiple devices losing the session means starting that comparison all over again.
What problems is the product solving and how is that benefiting you?
Design handoff used to end with fingers crossed hoping developers implemented it correctly across all screen sizes. Now I verify it myself on real devices before anything get signed off. Responsive layout breaks, motion timing inconsistencies, color rendering differences across screens, touch interaction behavior on mobile - all visible and fixable before users ever see them. BrowserStack gave me ownership of quality that I never had before as a designer.
Design
Made Testing Across Browsers and Devices Easier
Reviewed on May 29, 2026
Review provided by G2
What do you like best about the product?
I like how BrowserStack lets me test designs and websites on different browsers and devices without needing to own multiple systems. It helped me check responsive layouts, browser compatibility, and overall UI experience much faster. I used it to review Figma-based layouts and prototypes on different screen sizes to understand how the design would actually look for users. It was easy to integrate the Figma setup here. I found the platform easy to get started with, it works smoothly, and saves time compared to manually setting up different operating systems, browsers, etc. Pricing is decent, a little on the expensive side for me at the moment. One feature I found really useful was how quickly I could switch between browsers and devices during testing, which made it easier to catch UI issues early instead of testing everything manually.
What do you dislike about the product?
Some sessions felt like they were lagging, which kind of broke the flow of work. Other than that, I would like the free trial to give a bit more time for testing larger design flows.
What problems is the product solving and how is that benefiting you?
As a UI/UX designer, BrowserStack made it easier to see how my designs would actually look on different browsers and devices before they went live. I could quickly check responsiveness, catch weird spacing or layout issues, and get a better idea of what users would actually see. I also tried the Accessibility Design Toolkit in Figma, which helped spot things like low color contrast and accessibility issues between text and other design elements. I liked that some of the AI-powered accessibility checks could point out potential problems early, instead of me having to manually look for everything. Another thing I really liked was how it made designer-dev communication smoother. Instead of going back and forth with screenshots and explanations, we could look at the same browser or device setup and figure out issues much faster. Overall, it does save some time, reduces guesswork, and gives me more relief before handing designs off for development. I think