Save network request and response bodies to files
Introduced 2026-01-27 · score 0.93
HOW TO USE IT
When debugging a web app, call `get_network_request` for the target page and set `requestFilePath` and/or `responseFilePath` to save bodies; omit either path to return that body inline.
get_network_request({"pageId": <pageId>, "reqid": <requestId>, "requestFilePath": "<request-path>", "responseFilePath": "<response-path>"})WHY THIS HELPS
Inspect or retain network request and response bodies while debugging a repository's web application.
BEFORE THIS CHANGE
Retrieve the body inline by omitting `requestFilePath` and `responseFilePath`.
REQUIREMENTS AND LIMITATIONS
- Version: 0.14.0
- pageId (required): ID of the target page.
- reqid: Request ID; omit to use the currently selected request in the DevTools Network panel.
- requestFilePath: Absolute or relative path to save the request body; omit to return it inline.
- responseFilePath: Absolute or relative path to save the response body; omit to return it inline.
- Both path parameters are optional and accept absolute or relative paths.
FIRST-PARTY EVIDENCE
- https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.14.0
- https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/795
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/6d0e4cab28a8498c2783c1c0c6436c655de7b336/docs/tool-reference.md
Check the installed version and the source before using it. Entry JSON