visual-validate

Automate visual regression testing by driving a real MCP browser session to capture baseline and post-change screenshots, then compare them to detect layout differences. It also captures console errors and network requests to speed up regression validation.

Visual validation in browser automation is the process of capturing before and after screenshots during UI changes to detect visual regressions. You need it when validating UI updates after code commits or design changes to ensure layout consistency.

You do not strictly need Chrome DevTools MCP; Chrome DevTools is preferred, but Playwright is supported as a fallback. An available MCP is required to drive the real browser sessions, capture screenshots, and collect console output.

The best way to capture console errors and screenshots during UI regression testing is using a real-browser MCP session that automatically collects baseline and post-change visuals alongside console logs, network requests, and a summary verdict of the results.

Limitations of MCP-based visual validation include the requirement of an active MCP connection to drive the browser session. If neither Chrome DevTools nor Playwright MCP is available, the tool cannot capture screenshots, console output, or generate a summary verdict.