Browser Automation vs Chrome DevTools MCP

Browser Automation lists no tools and runs locally and Chrome DevTools MCP lists no tools and runs locally.

FactBrowser Automationio.github.mindstone/mcp-server-browser-automationChrome DevTools MCPio.github.secforge/chrome-devtools-mcp
ScoreNot checked yetNot checked yet
StatusNot checked yetNot checked yet
Tools00
Can write dataNo tools listedNo tools listed
RunsLocalLocal
Needs firstNode.jsNode.js
LicenceFSL-1.1-MITAPACHE-2.0
Latest version0.2.21.10.1004
Known advisories00
Works inClaude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, mcp-client-cli, oterm, TUUI, BoltAI, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLIClaude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, mcp-client-cli, oterm, TUUI, BoltAI, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI
Downloads last weekNot knownNot known
InstallInstall Browser AutomationInstall Chrome DevTools MCP

Scores and status come with our own checks, which have not run on these servers yet. The rest is from the publishers' registry entries, package registries and advisory databases.

Compare Browser Automation with othersCompare Chrome DevTools MCP with others