nodriver — Chrome browser automation vs Browserbase

nodriver — Chrome browser automation lists no tools and runs locally and Browserbase lists no tools and runs locally.

Factnodriver — Chrome browser automationio.github.andresolbach/nodriver-mcp-serverBrowserbaseio.github.browserbase/mcp-server-browserbase
ScoreNot checked yetNot checked yet
StatusNot checked yetNot checked yet
Tools00
Can write dataNo tools listedNo tools listed
RunsLocalLocal
Needs firstuvNode.js
LicenceNot statedAPACHE-2.0
Latest version2.6.12.1.1
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 nodriver — Chrome browser automationInstall Browserbase

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 nodriver — Chrome browser automation with othersCompare Browserbase with others