DOMShell vs Public Browser

In-depth architectural comparison of the DOMShell 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?

Choose DOMShell 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).
• Primary tools included: 38 MCP tools for Chrome browser control, Virtual filesystem mapped from the Accessibility Tree, Tab and window navigation.

Explore DOMShell 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).
• Primary tools included: PUBLIC_BROWSER_SCRIPT_TOKEN.

Explore Public Browser Details

Feature & Specification Comparison

Specification	DOMShell apireno Browser Automation	Public Browser Browser Automation
Summary
Category & Scope	Browser Automation	Browser Automation
Quality signal

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": {
    "apireno-domshell": {
      "command": "npx",
      "args": [
        "-y",
        "@apireno/domshell"
      ]
    }
  }
}

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

Related MCP Server Comparisons