What is the key difference between DOMShell and Mcp?

DOMShell belongs to the Browser Automation category with local stdio execution, while Mcp belongs to the Browser Automation category with cloud HTTP/SSE execution.

How do I install DOMShell or 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 Mcp free or paid?

DOMShell operates under a Free / Open Source model (No auth required). 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 2 views and 51 GitHub stars. Mcp lists 4 tools with 3 views and 6,949 GitHub stars.

Can I use both DOMShell and 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.

How do I install DOMShell or Mcp in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are DOMShell and Mcp free to use, or do they require API keys?

DOMShell is listed under a Free / Open Source model with No auth required . Mcp operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both DOMShell and Mcp at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both apireno-domshell and browsermcp-mcp as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, DOMShell has a Quality Score of 55 /100 ( Good ) with 2 views, 0 installs, and 51 GitHub stars. Mcp holds a Quality Score of 47 /100 ( Fair ) with 3 views, 0 installs, and 6,949 GitHub stars.

Side-by-Side Model Context Protocol Comparison

DOMShell vs Mcp

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

Mcp

Browser Automation · Remote HTTP/SSE

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

Verdict Summary: Choose DOMShell if you need specialized Browser Automation tools running via a local process. Choose Mcp if your workspace requires Browser Automation integration with remote web transport. 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: 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 Mcp when:

You need dedicated capabilities in the Browser Automation domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Local execution for low-latency browser automation, Uses existing browser profile to stay logged in, Stealth mode to avoid basic bot detection and CAPTCHAs.

Feature & Specification Comparison

Specification	DOMShell apireno Browser Automation	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)

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

Allows navigation and opening of URLs from the terminal

Supports isolated tab groups for session separation

Operates as a Chrome Extension with side panel terminal

Mcp Tools (4)

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"
      ]
    }
  }
}

Mcp Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "browsermcp-mcp": {
      "url": "https://browsermcp.io"
    }
  }
}

Frequently Asked Questions

DOMShell is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Mcp belongs to Browser Automation using remote streaming HTTP/SSE transport. Select DOMShell when you need capabilities focused on browser automation and Mcp when you require tools for browser automation.

More alternatives to DOMShell More alternatives to Mcp Browser Automation category hub