Does chrome-devtools-mcp have heap snapshot / memory analysis tools?
I'm using ChromeDevTools/chrome-devtools-mcp with an AI agent and want it to debug memory leaks and detached DOM nodes, but the server only exposed performance tracing tools like performance_start_trace. A full heap snapshot is too large for the agent to process. Has heap memory analysis, including snapshot comparison, been added to the MCP server?
Originally asked on GitHub: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/406
1 answer
Status: closed as completed. A contributor commented on 2026-03-31 that the first version of this shipped, and the issue was then closed; no version number or exact tool names were shared in the thread. The issue proposed three server-side analysis tools: memory_analyze_heap() for a current-state summary (total_heap_size, detached_dom_nodes, top_objects_by_retained_size), memory_start_diff() to store a baseline snapshot and return a diff_id, and memory_stop_diff(diff_id) to compare a final snapshot against that baseline and return heap_size_delta, new_detached_dom_nodes, and object_deltas. Because this thread is the feature request itself, it does not document the shipped API, so the actual tool names and JSON output may differ. General advice: check the chrome-devtools-mcp README and release notes for the shipped memory tools before relying on the proposed signatures.
Did this work for you?
Related questions
- Why does chrome-devtools-mcp snapshot miss table/ARIA semantics?
- Why is --load-extension ignored by chrome-devtools-mcp?
- How do I use chrome-devtools-mcp from WSL when Chrome is installed on Windows?
- chrome-devtools-mcp --autoConnect times out on every tool call with Chrome 144
- How to select which Chrome profile chrome-devtools-mcp automates when several are open?