Kronenberg & Grimm: Google Chrome MCP + Lighthouse Agentic Browsing

Key Takeaways:

• Google Chrome introduced its MCP and Google Chrome Canary 150.x now supports WebMCP while adding a "agentic-browsing" category to Lighthouse 13.3.0 audits

• WebMCP + Lighthouse:

  • whether the page exposes a clean accessibility tree

  • which WebMCP tools are registered (imperative + declarative form tools)

  • whether their input schemas validate

  • form coverage - which <𝚏𝚘𝚛𝚖> elements are annotated for agents and which are invisible to them

  • whether your llms.txt follows the recommendations

• Chrome DevTools MCP: "Audit diese URL top-down." Typischer Befund nach fuenf Sekunden:

  • LCP zwischen 3.5 und 4.8 Sekunden

  • INP regelmaessig ueber 300ms

  • 10 bis 16 Render-Blocking-Resources, ueberwiegend Third-Party

  • JS-Bundles ueber 1MB gzipped

  • Hydration-Mismatches oder Console-Errors auf 4 von 5 Seiten

• Kronenberg hebt hervor: Du kannst denselben Audit jetzt fuer 100 URLs parallel laufen lassen, ohne 100 Mal F12 zu druecken.

• I am really looking forward to incorporating this into a Page Check Skill

Sources:

• https://www.linkedin.com/posts/bastiangrimm_google-just-shipped-a-webmcp-audit-chrome-share-7465682409305427968-DChx/

• https://www.linkedin.com/posts/hannskronenberg_25-minuten-audit-pro-seite-manuell-in-devtools-share-7465692736231202816-8THm/

• https://github.com/ChromeDevTools/chrome-devtools-mcp

• https://webmcp.basgr.com/

• https://github.com/basgr/cf-webmcp

• https://www.linkedin.com/posts/dominikhorn_das-chrome-devtools-mcp-ist-da-und-ich-bin-ugcPost-7465757264918892544-b4dV/

• https://www.google.com/intl/de/chrome/canary/

• https://developer.chrome.com/docs/lighthouse/agentic-browsing/scoring