Chrome DevTools · 2026-07-03 · notable
Chrome DevTools MCP 1.5.0 — heap snapshot comparison lands for coding agents
Chrome DevTools MCP 1.5.0 ships two new memory-analysis tools for AI agents: get_heapsnapshot_duplicate_strings for spotting string-interning leaks, and heap-snapshot comparison for diffing memory between runs. Directory permissions were also hardened to 0o700.
Chrome DevTools MCP 1.5.0 gives coding agents a proper heap-snapshot diff workflow, plus tighter default file permissions.
What is it?
Chrome DevTools MCP is Google's official Model Context Protocol server that exposes Chrome DevTools browsing, tracing, and memory tools to AI coding agents. Version 1.5.0, tagged on July 3, focuses the release around heap-snapshot analysis — a piece of the DevTools surface agents previously had to script by hand.
How does it work?
The 1.5.0 release adds two heap-snapshot MCP tools. get_heapsnapshot_duplicate_strings surfaces the string-interning offenders that dominate real-world memory footprints, and a second set of tools lets an agent capture two snapshots and diff them to find growth between runs. The release also hardens output-directory permissions to 0o700 and validates paths against the extension's allow/block lists.
Why does it matter?
Memory regressions are one of the classes of browser bugs agents have historically been worst at reproducing — the fix loop needed hand-driven DevTools. With native heap-diff MCP tools, an agent can run a repro, snapshot, run again, snapshot, and hand back a concrete leak candidate without a human at the browser.
Who is it for?
Coding-agent authors, frontend perf engineers, browser-automation teams
Try it
npx chrome-devtools-mcp@1.5.0