Browserstack MCP Server

🚀 BrowserStack MCP Server

The BrowserStack MCP Server is a tool that integrates with BrowserStack to provide specific services, facilitating automated and manual testing.

🚀 Quick Start

The BrowserStack MCP Server combines the power of BrowserStack and the MCP protocol. It enables seamless integration with popular coding assistants and testing tools, enhancing the development and testing experience.

📦 Installation

Step 1: Create a BrowserStack Account

• Visit BrowserStack Account Settings.
• Note down your username and access_key.

Step 2: Ensure Node Version >= v18.0

It is recommended to use the LTS version: v22.15.0.

node --version

Step 3: Install the MCP Server

In VSCode (for Copilot's Agent Mode):

Add the following content to .vscode/mcp.json:

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

Click the Start button in VSCode to start the server.

In Cursor:

Add the following content to .cursor/mcp.json:

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

In Claude Desktop:

Add the following content to ~/claude_desktop_config.json:

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

✨ Features

Recommended MCP Clients

• Github Copilot or Cursor: Ideal for automated testing and debugging.
• Claude Desktop: Suitable for manual testing.

📚 Documentation

Important Notes

⚠️ Important Note

1. The BrowserStack MCP Server is under active development and currently only supports some features of the MCP specification. More features are coming soon.
2. Tool invocations rely on LLM (Large Language Model), which may lead to non - deterministic behavior and unexpected results.

Contribution Guidelines

We welcome contributions! Please refer to Contributing Guidelines to get started.

Support

• Check out our Documentation.
• If you encounter any issues, please submit them in the GitHub Repository.
• Contact our Support Team.

Future Features Preview

More updates are coming soon! If you have any suggestions, please open an issue for discussion.

Resource Links

• BrowserStack Testing Platform
• MCP Protocol Documentation
• Device Matrix
• Accessibility Testing