DOMShell vs Agent Web Interface

In-depth architectural comparison of the DOMShell and Agent Web Interface 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: Maps browser tabs and windows to directories, Represents DOM elements as files and folders via Accessibility Tree, Supports standard Linux commands for navigation and interaction.

Explore DOMShell Details

Choose Agent Web Interface 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).
• You have access to required keys: CHROME_EXECUTABLE_PATH, PORT.
• Primary tools included: Compact semantic page snapshots including regions and content, Stable element IDs (eids) for reliable element referencing, Integration with Puppeteer and Chrome DevTools Protocol.

Feature & Specification Comparison

Specification	DOMShell apireno Browser Automation	Agent Web Interface lespaceman Browser Automation
Summary
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": {
    "apireno-domshell": {
      "command": "npx",
      "args": [
        "-y",
        "@apireno/domshell"
      ]
    }
  }
}

{
  "mcpServers": {
    "lespaceman-agent-web-interface": {
      "command": "npx",
      "args": [
        "-y",
        "@drisp/browser-mcp"
      ],
      "env": {
        "CHROME_EXECUTABLE_PATH": "YOUR_CHROME_EXECUTABLE_PATH_HERE",
        "PORT": "YOUR_PORT_HERE"
      }
    }
  }
}

Related MCP Server Comparisons