mcp

The BrowserStack MCP Server integrates BrowserStack’s testing capabilities into an MCP-enabled workflow. It exposes prompts and natural language commands that let you manage test cases, run manual and automated tests, debug issues, and even apply fixes directly from within your IDE or preferred MCP client. With this server you can create test management flows, trigger test runs, fetch results, and leverage BrowserStack’s AI-assisted tooling to analyze failures and propose fixes. The server is designed to be used in conjunction with MCP-enabled clients to streamline test orchestration across BrowserStack’s cloud devices and browsers.

Once running, you can interact with the server using natural language prompts such as creating test projects, adding or listing test cases, launching test runs, or requesting AI-assisted debugging of failures. The capabilities extend to automated testing pipelines (Playwright, Selenium, and other frameworks) and to accessibility and test management features, allowing you to generate or repair test artifacts in-context. This enables a cohesive workflow where you stay in your development environment while performing complex testing tasks across BrowserStack’s platform.

Prerequisites:

• Node.js version 18 or higher
• npm (comes with Node.js)

Option A: One-click MCP setup (recommended for IDE integrations)

• Use the one-click setup buttons in the BrowserStack MCP README to install the MCP server in your IDE (VS Code or Cursor).

Option B: Local installation via npm

1. Ensure Node.js is installed (v18.x or newer).
2. Install the MCP server globally (optional) or use npx to run directly:
   • Global install (optional): npm install -g @browserstack/mcp-server
   • Run with npx (no global install required): npx -y @browserstack/mcp-server
3. Start the MCP server (depending on your setup):
   • If installed globally and script is provided, run: mcp-server
   • Or invoke directly via npx when you need to start: npx -y @browserstack/mcp-server

Note: If you plan to run the server as part of a larger project, you may prefer to add it as a devDependency and run it via an npm script in your package.json.

Environment and configuration tips:

• Node version: Ensure you are on Node >= 18.0.0 as recommended.
• If you encounter network or npm resolution issues while running via npx, clear npm cache or try running with a clean environment.
• The MCP server relies on BrowserStack authentication in certain prompts; ensure your BrowserStack credentials or API keys are configured in your environment where required.
• When integrating with CI/CD, consider exposing the MCP server as a service within your pipeline and configure proper environmental variables for authentication and project scopes.
• If you need to customize prompts or behaviors, check the MCP client documentation for mapping commands to BrowserStack actions and adjusting test management workflows.