Hwatu MCP Server

Verification browser for coding agents: headless WebKit, DOM eval, screenshots, pixel-diff.

Local serverstdio

What is the Hwatu MCP server?

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.

What you get

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.

  • Headless / background / focused as a per-window property, switchable live
  • Human hand-off: hwatu focus drops the live session into your tiling WM
  • Pixel-diff scoring: match percent + diff regions + heatmap (diff)
  • Animations as numbers: duration, easing, velocity (motion)
  • Deterministic animation frames: pin all animations at time t (seek)
  • Page state as JSON, tokens not pixels (snapshot)

What the assistant can call

Once Hwatu is connected, these are the calls the assistant has available:

  • hwatu"the coldest warm daemon": engine hot, everything else absent

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

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.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the hwatu mcp server does with a few real requests.

Available tools

ToolWhat it does
hwatu**"the coldest warm daemon"**: engine hot, everything else absent

Example prompts to try

  • Use Hwatu to hwatu.

Frequently asked questions

It connects Hwatu to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (hwatu) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Hwatu directly.