Network Request Interception and URL Replacement

Is your feature request related to a problem? Please describe.

Currently there is no automated way through the Chrome DevTools MCP server to intercept and modify network requests. Developers can manually override or redirect resources using the Chrome DevTools UI (e.g., Local Overrides or Response Overrides), but these actions must be done interactively and cannot be scripted or integrated into automated measurement workflows. This becomes a blocker when trying to test development versions of scripts against real production pages.
This become a blocker also to automate experiments in CI or lab environments by using built scripts before doing a production release.
In this issue I'm referring to script but it could be useful also for others resources as is done in the Chrome DevTools UI.

Example real-world impact: if a production page loads a script at https://bar.foo.com/scriptWeAlreadyHaveInWebsite.js, there is no way via MCP today to replace that with a development version and collect metrics without doing it manually in the browser.

Describe the solution you'd like

Add support in the Chrome DevTools MCP server for programmatic network request interception and modification, including:

• Redirect requests to a different URL
• Override responses with custom content (remote or local file)

Specifically, the ability to:

• Match a network request (by URL or pattern)
• Redirect it to a different URL (e.g., dev/newVersion.js)
• Optionally serve a custom or local file as the response

This would expose the same functionality found in the DevTools UI (“Override content” / “Local Overrides”) through MCP, enabling automation and tooling scenarios.

Describe alternatives you've considered

The only alternative currently available is to manually use Chrome DevTools UI (https://developer.chrome.com/docs/devtools/overrides) or by developing a custom Chrome Extension.

Additional context

No response

Start by reviewing the Chrome DevTools Overrides documentation linked in the issue and the repository’s MCP server entry points. Define how URL or pattern matching, redirects, custom responses, and local files should work, then verify that the result supports scripted development-versus-production experiments in CI or lab environments.