← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionZeroTokenRecord once, automate forever. Lightweight MCP for AI agent browser automation with trajectory recording and low-token script replay.Chrome DevTools MCPThe Chrome team's official MCP server exposing Chrome DevTools capabilities to AI assistants
FMRS54 / 100 · D76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions8 / 2012 / 20
Maintenance12 / 2017 / 20
Documentation13 / 2017 / 20
Setup experience11 / 2017 / 20
Best for
  • Record-once, run-forever scheduled or repetitive tasks such as daily logins and timed scraping
  • Agent setups that want lower token cost instead of step-by-step LLM reasoning on every run
  • Projects needing rich browser primitives: multi-tab, iframes, file upload/download, drag and drop
  • Automation flows that need element fingerprints and adaptive re-location to survive site redesigns
  • Frontend developers who want AI-assisted web debugging and performance analysis
  • Scenarios that need browser automation and performance diagnostics in the same tool
Not for
  • Environments that cannot run Playwright/Chromium or install a browser
  • Clients that rely only on stdio while needing browser state across calls (the README states command mode spawns a new process per tool call, destroying the browser instance)
  • Production-critical systems requiring official commercial support or an SLA
  • Setups that do not accept local SQLite persistence of trajectories, screenshots and sessions
  • Cases that only need to scrape page text without performance analysis or complex interaction (a lighter scraping tool is a better fit)
Required permissions
  • Local filesystem read/write (SQLite database zerotoken.db, upload and download paths)
  • Network access (target websites, Playwright/Chromium download)
  • Launch and control a local Chromium browser process
  • In OpenClaw, run a local HTTP service on a listening port (default 8000)
  • Requires a local Chrome browser instance to run
  • navigate_page can visit any URL; type_text/fill_form and similar tools can enter arbitrary content into the page
Risks and side effects
  • Scripts act as a real browser and perform clicks, typing, uploads and downloads, so mistakes can change data or submit forms unintentionally
  • Trajectories store page state and screenshots (base64 images may contain sensitive data) on disk in SQLite, creating privacy and credential-leak risk
  • Fingerprint masking via browser_init(stealth=true) may violate target sites' terms of service
  • Depends on target page structure: selector failure remains the main instability factor (60% per the README), so scripts may break after redesigns
  • HTTP mode listens on 0.0.0.0 by default and can be called by others if exposed to untrusted networks
  • Browser automation tools can access and manipulate the content of open pages — use only in a trusted development/test environment
  • performance_start_trace and similar tracing tools continuously record browser activity — avoid leaving them running on pages containing sensitive information
Supported clientsOpenClaw, CursorClaude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Cline, Amp, Kiro, Antigravity
Tools3322