Verification browser for coding agents: headless WebKit, DOM eval, screenshots, pixel-diff.
Hwatu MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Verification browser for coding agents: headless WebKit, DOM eval, screenshots, pixel-diff.
hwatu is a visual verification harness for coding agents, built as a WebKit daemon. Instead of "looks right to me", your agent gets one-call verified page checks in ~35 ms, pixel-diff scores it can climb, animations as numbers, and headless windows that never steal your focus, at any parallelism.
Once Hwatu is connected, these are the calls the assistant has available:
hwatu — "the coldest warm daemon": engine hot, everything else absentSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Hwatu's toolset — hwatu — is a fair guide to whether it matches your workflow. It is maintained by hongnoul; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Hwatu's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| hwatu | **"the coldest warm daemon"**: engine hot, everything else absent |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.