WebRun Browser Automation vs Public Browser

In-depth architectural comparison of the WebRun Browser Automation and Public Browser MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

W

Choose WebRun Browser Automation when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore WebRun Browser Automation Details

Choose Public Browser when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Public Browser Details

Feature & Specification Comparison

Specification	W WebRun Browser Automation Browser Automation	Public Browser Browser Automation
Summary	Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.	The most token-efficient MCP server for Chrome automation — a Playwright MCP alternative.
Category & Scope	Browser Automation	Browser Automation

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "webrun-browser-automation": {
      "command": "npx",
      "args": [
        "-y",
        "webrun-browser-automation"
      ]
    }
  }
}

{
  "mcpServers": {
    "public-browser": {
      "command": "npx",
      "args": [
        "-y",
        "public-browser@latest"
      ]
    }
  }
}

Related MCP Server Comparisons