BrowserStack MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BROWSERSTACK_USERNAME | Yes | Your BrowserStack username from Account Settings | |
| BROWSERSTACK_ACCESS_KEY | Yes | Your BrowserStack access key from Account Settings |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| runTestsOnBrowserStackC | Use this tool to get instructions for running tests on BrowserStack. |
| runAppLiveSessionB | Use this tool when user wants to manually check their app on a particular mobile device using BrowserStack's cloud infrastructure. Can be used to debug crashes, slow performance, etc. |
| runBrowserLiveSessionB | Use this tool when user wants to manually check their website on a particular browser and OS combination using BrowserStack's cloud infrastructure. Can be used to debug layout issues, compatibility problems, etc. |
| getFailuresInLastRunA | Use this tool to debug failures in the last run of the test suite on BrowserStack. Use only when browserstack.yml file is present in the project root. |
| startAccessibilityScanC | Use this tool to start an accessibility scan for a list of URLs on BrowserStack. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: getFailuresInLastRun is for debugging test failures, runAppLiveSession is for manual mobile app testing, runBrowserLiveSession is for manual website testing, runTestsOnBrowserStack is for test execution instructions, and startAccessibilityScan is for accessibility scanning. The descriptions reinforce these distinct use cases, making tool selection unambiguous.
The naming follows a mixed pattern: three tools use 'run' as a verb (runAppLiveSession, runBrowserLiveSession, runTestsOnBrowserStack), while getFailuresInLastRun uses 'get' and startAccessibilityScan uses 'start'. All tools use camelCase consistently, but the verb choices vary, creating a readable but not fully consistent convention across the set.
With 5 tools, this is well-scoped for a BrowserStack testing server. Each tool serves a distinct and essential function in the testing workflow—debugging, manual testing (app and browser), test execution, and accessibility scanning—making the count appropriate without being too sparse or bloated.
The toolset covers key BrowserStack functionalities: debugging failures, manual testing for apps and browsers, test execution guidance, and accessibility scanning. Minor gaps might include automated test reporting or configuration management, but the core workflows are well-covered, allowing agents to perform most common testing tasks effectively.