browser
browser
Persistent Chrome/CDP control via puppeteer-core. The primary interaction model
is snapshot → stable ref → action. Selectors and coordinates are fallbacks only.
Output size decides where a read lands: at or above the server's inline
threshold (PAYLOAD_THRESHOLD_BYTES in mcp-browser/src/lib/payload.ts) the
payload is written to a temp file and the tool returns the path; below it the
payload comes back inline with written: false and no path. Handle both cases —
see references/interaction.md in this skill directory for the per-tool result
fields. Screenshots, PDFs, traces, HAR, Lighthouse reports, and saved storage
state are always files, however small.
Prerequisites
Call browser_connect before any other tool. Mode launch spawns (or reuses)
a Chrome process; mode attach connects to a running Chrome via browser_url
or ws_endpoint.