ChromeDevTools
Allow saving performance trace as a file
Is your feature request related to a problem? Please describe.
AS A web performance engineer developing a tool to run automated performance audits using this MCP server, I'D LIKE TO have the ability to save a web performance trace locally, SO THAT I can upload it to Trace Cafe and analyze it myself / share it with the customer.
The problem is that currently this MCP server doesn't have the feature to save a performance trace locally.
Describe the solution you'd like
AS A web performance engineer developing a tool to run automated performance audits using this MCP server, I'D LIKE TO have the ability to save a web performance trace locally, SO THAT I can upload it to Trace Cafe and analyze it myself / share it with the customer.
It this MCP server was able to write the trace to file, it would solve my problem.
Describe alternatives you've considered
I don't think I have many alternatives other then opening devtools and auditing web performance myself.
Additional context
I'm developing a tool to run automated performance audits using this MCP server.
I think this could be interesting for reproducibility and audit scenarios too. @OrKoN @sebastianbenz thoughts?
Definitely agree, reproducibility for any kinds of automated checks would definitely be really good to enable.
Our plan is to build a tool that monitors RUM data for anomalies. If an anomaly is detected, we would like to use the MCP server to reproduce the problem locally and create a trace automatically. Therefore, it would be great if the MCP server would be able to annotate the trace to highlight areas that need improvement and store it locally or even upload it to Trace Cafe.
Would you be interested in uncompressed json or a .json.gz file? Draft https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/686
Doesn't really matter to us, gZipped would be better because it takes less bandwidth to upload it to trace.cafe, but both would work