Mcp Server Browser vs DOMShell

Side-by-side comparison of two Model Context Protocol servers โ€” install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
Mcp Server Browser logo
๐Ÿ“‚ Browser Automation
DOMShell logo
DOMShell
apireno
๐Ÿ“‚ Browser Automation
SummaryBrowser automation capabilities using Puppeteer, both support local and remote browser connection.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.
Quality signal41/100 (Fair)52/100 (Fair)
Install pathnpx ยท highnpx ยท high
Engagement 2 0 0 38,500 2 0 0 51
ToolsPuppeteer-based browser automationSupports local browser connectionsSupports remote browser connectionsMaps browser windows and tabs to top-level directoriesRepresents Accessibility Tree nodes as nested directories and filesSupports standard Linux commands: ls, cd, cat, grep, click, find, navigate, openProvides isolated tab group sessions for session managementOperates via a Chrome Side Panel terminal interfaceNo site-specific adapters required; works on any website
Verified / officialNoNo
Open listingView Mcp Server BrowserView DOMShell
More alternatives to Mcp Server BrowserMore alternatives to DOMShellBrowser Automation category

Other servers like Mcp Server Browser