chrome-devtools-mcp adds get_heapsnapshot_object_details
Introduced 2026-08-10 · score 0.95
HOW TO USE IT
When debugging memory use, enable memory debugging and call `get_heapsnapshot_object_details` with a `.heapsnapshot` path and node ID to retrieve the object's size, type, distance, and DOM detachedness.
get_heapsnapshot_object_details({"filePath":"<path-to-file.heapsnapshot>","nodeId":<node-id>})WHY THIS HELPS
Inspect a specific object in a heap snapshot while debugging memory use.
REQUIREMENTS AND LIMITATIONS
- Version: 1.7.0
- --memoryDebugging=true (required): Enables memory debugging tools.
- filePath (required): Path to a `.heapsnapshot` file to read.
- nodeId (required): Node ID of the object to inspect.
- Prerequisite: Start the MCP server with `--memoryDebugging=true` enabled.
- Prerequisite: Provide a path to a `.heapsnapshot` file and the target node ID.
- Requires the `--memoryDebugging=true` flag.
- Requires a path to a `.heapsnapshot` file and a node ID.
FIRST-PARTY EVIDENCE
- https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v1.7.0
- https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/2374
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/chrome-devtools-mcp-v1.7.0/docs/tool-reference.md
Check the installed version and the source before using it. Entry JSON