Summary
Browser automation with the debugging surface attached.
Beyond clicking and typing it hands back console messages, the network request list and a depth-limited DOM tree — which is what turns it from a scraper into something an agent can diagnose a page with. Scrolling reports where it started and finished, so the agent can tell a no-op from a move.
What it is
A Playwright-based browser automation server: open a browser, point it at a URL, then interact with the page or pull data out of it.
What you get
- Session control with openBrowser and closeBrowser, headless or visible
- Navigation and interaction: navigate, goForward, goBack, click, type, hover, dragAndDrop, selectOption and pressKey
- Coordinate-level mouse control with moveMouse, mouseMove, mouseClick and mouseDrag, plus resize and scroll
- Waiting that is not a sleep: waitForText and waitForSelector
- Page readback: getPageSource, getPageText, getPageTitle, getPageUrl, getMetaTags, getScripts and getStylesheets
- Structured extraction: getLinks, getImages, getForms, getElementContent, and getElementHierarchy for the DOM tree to a depth you choose
- Diagnostics: getConsoleMessages and getNetworkRequests
- executeJavaScript and evaluateWithReturn run your own script in the page
- screenshot and takeScreenshot capture the full page, the viewport or a single element; uploadFiles and handleDialog cover file inputs and alerts
Requirements
Node, plus the Playwright browser binaries installed once. Built from source and run as a local process, with no account or key. Every tool needs a live session, so the browser has to be opened first.
Setup effort
One command — npm install && npm run build && npx playwright install