chrome-devtools-mcp performance tools accept filePath for raw trace output
Introduced 2026-01-15 · score 0.95
HOW TO USE IT
When profiling a web application, set `filePath` on `performance_start_trace` or `performance_stop_trace` to save the raw trace; use `.json.gz` for compressed output or `.json` for uncompressed output.
performance_start_trace({"pageId": <pageId>, "filePath": "<trace.json.gz>"})performance_stop_trace({"pageId": <pageId>, "filePath": "<trace.json>"})WHY THIS HELPS
When profiling a repository's web application, save raw performance trace data to a file for inspection.
REQUIREMENTS AND LIMITATIONS
- Version: 0.13.0
- pageId (required): ID of the target page.
- filePath: Absolute path or path relative to the current working directory for raw trace output; `.json.gz` is compressed and `.json` is uncompressed.
- autoStop (required): On `performance_start_trace`, determines whether recording stops automatically.
- reload (required): On `performance_start_trace`, determines whether the target page reloads after tracing starts.
- Prerequisite: If `reload` or `autoStop` is true, navigate to the right URL before starting the trace.
- `filePath` is optional.
- The path may be absolute or relative to the current working directory.
FIRST-PARTY EVIDENCE
- https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.13.0
- https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/686
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/chrome-devtools-mcp-v0.13.0/docs/tool-reference.md
Check the installed version and the source before using it. Entry JSON