@manzoid2/browser-tools
v1.0.2
Published
Minimal Puppeteer-based browser automation toolkit for AI coding agents
Maintainers
Readme
Browser Tools
Minimal Puppeteer-based browser automation toolkit for AI coding agents. Inspired by Mario Zechner's approach.
Philosophy
Instead of heavy MCP servers, these are simple bash-callable scripts that leverage the agent's existing JavaScript knowledge. Total documentation: ~225 tokens vs 13k+ for MCP equivalents.
Tools
start.js [profile] [--copy-profile]
Launches Chrome with remote debugging on port 9222.
./start.js # Use default profile
./start.js work # Use named profile
./start.js work --copy-profile # Copy Chrome profile for authenticated sessionsnavigate.js [--new-tab]
Navigate to a URL.
./navigate.js https://example.com
./navigate.js https://example.com --new-tabevaluate.js "" | --file
Execute JavaScript in the current page context.
./evaluate.js "document.title"
./evaluate.js "document.querySelectorAll('a').length"
./evaluate.js --file script.jsscreenshot.js [output-path] [--full-page]
Capture screenshot of current page.
./screenshot.js
./screenshot.js output.png
./screenshot.js output.png --full-pageUsage with Claude Code
Add this directory to your session:
/add-dir ~/code/src/manzoid/browser-toolsThen Claude can use these tools by calling the scripts directly via Bash.
Why This Over MCP?
- Token efficient: Minimal docs, agent already knows JavaScript
- Composable: Output goes to disk, can be chained
- Extensible: Add new tools easily without versioning hell
- Simple: Just Node.js scripts, no protocol layer
