UXMUXMachine
Try it with a URL Sign in ESEN

UXMachine or Chrome DevTools MCP: which one should your AI agent use?

Use Chrome DevTools MCP when your AI agent needs to investigate a live page: performance traces, network requests, console messages and on-demand Lighthouse audits. Use UXMachine to repeat the same published checks on your live site and compare them with the previous measurement.

What Chrome DevTools MCP does

  • An open-source MCP server from Google, now presented as "Chrome DevTools for agents", under the Apache 2.0 license.
  • Lets a coding agent interact with and inspect a live Chrome browser: navigation, clicks, forms, screenshots, console messages and network requests.
  • Records performance traces and extracts Chrome DevTools performance insights.
  • Can emulate viewports, network and CPU conditions, dark or light colour schemes, contrast preferences and reduced motion.
  • Its Lighthouse tool audits accessibility, SEO, best practices and agentic browsing. It excludes performance, which is handled through performance traces.
  • Launches Chrome on your machine by default, or connects to a Chrome that is already running.
  • By default it collects usage statistics, and its performance tools may send trace URLs to Google's CrUX API. Both can be turned off separately.
  • It does not document a history of website checks comparable to UXMachine's measurement history.

What UXMachine does

  • Opens up to 11 pages of a site at 1280×800 and 390×844. The browser used for the measurement runs on UXMachine's servers, so you do not need Chrome on your machine for the check.
  • Runs a fixed, public list of checks and lists what it observed, with evidence, and what it could not check.
  • When there is a previous comparable measurement of the same site, it reports what is new, still observed, observed again, no longer observed or not comparable, and what could not be checked.

When to use which

  • Chrome DevTools MCP, to investigate: why a page is slow, which request fails, what the console says, or to interact with the page.
  • UXMachine, for a repeatable check of the published site after every change, and to know which observations changed since last time.
  • Both: Chrome DevTools MCP while fixing; UXMachine to check the result once it is published.

Do not use UXMachine to debug a live page: performance traces, failing requests, console errors or interaction. Use Chrome DevTools MCP for that.

This page compares documented features, not results on your site. UXMachine does not replace a full audit or testing with people. Checked on 19 October 2026.

Sources: Chrome DevTools MCP README · Lighthouse tool source