What is the key difference between DOMShell and Browsermcp MCP?

DOMShell belongs to the Browser Automation category with local stdio execution, while Browsermcp MCP belongs to the Browser Automation category with local stdio execution.

How do I install DOMShell or Browsermcp MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are DOMShell and Browsermcp MCP free or paid?

DOMShell operates under a Free / Open Source model (No auth required). Browsermcp MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

DOMShell lists 6 tools with 3 views and 54 GitHub stars. Browsermcp MCP lists 5 tools with 5 views and 7,155 GitHub stars.

Can I use both DOMShell and Browsermcp MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

DOMShell vs Browsermcp MCP

In-depth architectural comparison of the DOMShell and Browsermcp MCP 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.

At a Glance & Executive Verdict

DOMShell

Browser Automation · Local stdio

Quality: 55/100 (Good) | Auth: No auth required

Browsermcp MCP

Browser Automation · Local stdio

Quality: 40/100 (Fair) | Auth: No auth required

Verdict Summary: Choose DOMShell if you need specialized Browser Automation tools running via a local process. Choose Browsermcp MCP if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

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 Browsermcp MCP 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: Local browser automation, Chrome extension integration, Existing profile and logged-in session support.

Explore Browsermcp MCP Details

Feature & Specification Comparison

Specification	DOMShell apireno Browser Automation	Browsermcp MCP browsermcp Browser Automation
Summary	Browse the web using filesystem commands (ls, cd, grep, click). 38 MCP tools map Chrome's Accessibility Tree to a virtual filesystem via a Chrome Extension.	Browser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
Category & Scope	Browser Automation

Tools & Capabilities Breakdown

DOMShell Tools (6)

38 MCP tools for Chrome browser control

Virtual filesystem mapped from the Accessibility Tree

Tab and window navigation

Filesystem commands for search and interaction

Chrome tab-group session isolation

Side Panel terminal interface

Browsermcp MCP Tools (5)

Local browser automation

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).

DOMShell Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "apireno-domshell": {
      "command": "npx",
      "args": [
        "-y",
        "@apireno/domshell"
      ]
    }
  }
}

Browsermcp MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "browsermcp-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "browsermcp-mcp"
      ]
    }
  }
}

Frequently Asked Questions

DOMShell is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Browsermcp MCP belongs to Browser Automation using local stdio subprocess. Select DOMShell when you need capabilities focused on browser automation and Browsermcp MCP when you require tools for browser automation.

More alternatives to DOMShell More alternatives to Browsermcp MCP Browser Automation category hub