drio
Open app

mcp-browser-tester

Source

Allow MCP server to operate browser for testing purposes

Catalog onlyCatalog onlySTDIO

Overview

The mcp-browser-tester is a tool that allows the MCP server to operate a web browser for testing purposes, enabling automated testing of web applications.

To use mcp-browser-tester, integrate it with your MCP server setup and configure the necessary parameters to initiate browser sessions for testing.

  • Automated browser control for testing web applications - Integration with MCP server for seamless operation - Support for various testing scenarios and configurations
  1. Conducting automated regression tests on web applications.
  2. Performing load testing by simulating multiple browser sessions.
  3. Validating user interface elements and functionality through automated scripts.

Add to your AI client

Use these steps to connect mcp-browser-tester in Cursor, Claude, VS Code, and other MCP-compatible apps. The same JSON appears in the Use with menu above for one-click copy.

Cursor

Add this to your .cursor/mcp.json file in your project root, then restart Cursor.

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-browser-tester-rt96-hub": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-browser-tester-rt96-hub"
      ]
    }
  }
}

Claude Desktop

Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)

{
  "mcpServers": {
    "mcp-browser-tester-rt96-hub": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-browser-tester-rt96-hub"
      ]
    }
  }
}

Claude Code

Add this to your project's .mcp.json file. Claude Code will detect it automatically.

.mcp.json (project root)

{
  "mcpServers": {
    "mcp-browser-tester-rt96-hub": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-browser-tester-rt96-hub"
      ]
    }
  }
}

VS Code (Copilot)

Add this to your .vscode/mcp.json file. Requires the GitHub Copilot extension with MCP support enabled.

.vscode/mcp.json

{
  "servers": {
    "mcp-browser-tester-rt96-hub": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-browser-tester-rt96-hub"
      ]
    }
  }
}

Windsurf

Add this to your Windsurf MCP config file, then restart Windsurf.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcp-browser-tester-rt96-hub": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-browser-tester-rt96-hub"
      ]
    }
  }
}

Cline

Open Cline settings, navigate to MCP Servers, and add this server configuration.

Cline MCP Settings (via UI)

{
  "mcpServers": {
    "mcp-browser-tester-rt96-hub": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-browser-tester-rt96-hub"
      ]
    }
  }
}

FAQ

Can mcp-browser-tester be used with any web application?

Yes! It can be configured to work with any web application that is accessible via a browser.

Is mcp-browser-tester free to use?

Yes! It is open-source and available under the MIT license.

How do I report issues or contribute to mcp-browser-tester?

You can report issues or contribute by visiting the GitHub repository at https://github.com/rt96-hub/mcp-browser-tester.

Browser automation