---
next_cursor: eyJzY29yZSI6MCwic2VxIjozNjAsInNpbmNlIjpudWxsLCJ0b29sIjoiY2hyb21lLWRldnRvb2xzLW1jcCIsInYiOjF9
has_more: true
next: https://sincecutoff.com/v1/changes.md?tool=chrome-devtools-mcp&score=0&cursor=eyJzY29yZSI6MCwic2VxIjozNjAsInNpbmNlIjpudWxsLCJ0b29sIjoiY2hyb21lLWRldnRvb2xzLW1jcCIsInYiOjF9
items: 10
---
# sincecutoff.com changes: chrome-devtools-mcp

## chrome-devtools-mcp can selectively ignore default Chrome launch arguments (chrome-devtools-mcp, 2026-01-15)
Published 2026-10-13
- slug: chrome-devtools-mcp-can-selectively-ignore-default-chrome-launch-arguments-a4cbab763318
- score: 0.90

How to use it:

When the MCP server launches Chrome and you need to omit selected Puppeteer default flags, repeat `--ignore-default-chrome-arg` for each flag to ignore. The option does not apply when connecting to an already running Chrome.

Examples:

```
{"mcpServers":{"chrome-devtools":{"command":"npx","args":["-y","chrome-devtools-mcp@0.13.0","--ignore-default-chrome-arg=--enable-automation","--ignore-default-chrome-arg=--disable-extensions"]}}}
```

- why_it_matters: When debugging or testing requires Chrome to launch without selected Puppeteer defaults, configure chrome-devtools-mcp with the arguments to ignore.
- before: There was no way to opt out of Puppeteer's default Chrome launch arguments.
- sources: <https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.13.0>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/729>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/9a51af219fc9216cd463bef9363716283f41f36a/README.md>
- gotchas: "Version: 0.13.0"; "--ignore-default-chrome-arg / --ignoreDefaultChromeArg: Array option; explicitly disables selected default Chrome arguments. Only applies when chrome-devtools-mcp launches Chrome. Repeat for each argument to ignore."; "Prerequisite: Node.js v20.19 or newer maintenance LTS, Chrome current stable or newer, and npm."; "Only applies when Chrome is launched by chrome-devtools-mcp."; "The option is an array and allows selectively ignoring specific default Chrome launch arguments."

## chrome-devtools-mcp performance tools accept filePath for raw trace output (chrome-devtools-mcp, 2026-01-15)
Published 2026-10-13
- slug: chrome-devtools-mcp-performance-tools-accept-filepath-for-raw-trace-output-e4d9c470b72a
- 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.

Examples:

```
performance_start_trace({"pageId": <pageId>, "filePath": "<trace.json.gz>"})
```

```
performance_stop_trace({"pageId": <pageId>, "filePath": "<trace.json>"})
```

- why_it_matters: When profiling a repository's web application, save raw performance trace data to a file for inspection.
- sources: <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>
- gotchas: "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."

## Emulate device viewport and user agent (chrome-devtools-mcp, 2026-01-27)
Published 2026-10-13
- slug: emulate-device-viewport-and-user-agent-f91aff788a2d
- score: 0.96

How to use it:

When checking a page under a mobile or different desktop device configuration, call `emulate` with `viewport` and/or `userAgent`; set either to null to reset its override.

Examples:

```
emulate({"viewport": <viewport-value>, "userAgent": <user-agent-string>})
```

- why_it_matters: Check a web page under a mobile or different desktop device configuration.
- sources: <https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.14.0>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/798>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/a8169676f920f88965a2574f53affe15c1278b43/docs/tool-reference.md>
- gotchas: "Version: 0.14.0"; "viewport: Viewport override; set to null to reset to the default viewport. Its value format is not specified in this version's docs."; "userAgent: User-agent override; set to null to clear it."; "Both attributes are optional."; "The recommended way is to emulate via the MCP server instead of a parallel DevTools session."; "Docs conflict: Current official docs describe viewport as a formatted string and clearing userAgent with an empty string; the version 0.14.0 docs instead specify unknown value types and null resets. This card follows the 0.14.0 behavior."

## Input tools default to omitting snapshots (chrome-devtools-mcp, 2026-01-27)
Published 2026-10-13
- slug: input-tools-default-to-omitting-snapshots-d6b44ec44b30
- score: 0.91

How to use it:

When an input action does not need an updated page snapshot, call the input tool without `includeSnapshot`; set `includeSnapshot: true` to include one in the response.

Examples:

```
click({uid: "<element-uid>"})
```

```
fill({uid: "<element-uid>", value: "<text>"})
```

```
click({uid: "<element-uid>", includeSnapshot: true})
```

- why_it_matters: Use browser input tools when an updated page snapshot is unnecessary.
- before: Use the input tool with its default behavior, which regenerated snapshots.
- sources: <https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.14.0>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/821>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/4b8e9f287572e0a95c30b5ca612acf08bf79595b/docs/tool-reference.md>
- gotchas: "Version: 0.14.0"; "includeSnapshot: Whether to include a snapshot in the response; defaults to false."; "`includeSnapshot` is optional and defaults to false."

## new_page accepts a background parameter (chrome-devtools-mcp, 2026-01-27)
Published 2026-10-13
- slug: new-page-accepts-a-background-parameter-403d65c995c2
- score: 0.95

How to use it:

When opening a page while keeping the current page in front, call `new_page` with `background: true`. Provide the URL to load.

Examples:

```
new_page({"url":"<URL>","background":true})
```

- why_it_matters: Open a new browser page while keeping the current page in front.
- before: Call `new_page` to open a page in the foreground.
- sources: <https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.14.0>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/837>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/tool-reference.md>
- gotchas: "Version: 0.14.0"; "url (required): URL to load in a new page."; "background: Whether to open the page in the background without bringing it to the front; defaults to false (foreground)."; "The optional boolean parameter defaults to false (foreground)."

## Save network request and response bodies to files (chrome-devtools-mcp, 2026-01-27)
Published 2026-10-13
- slug: save-network-request-and-response-bodies-to-files-46b6f442a75a
- 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.

Examples:

```
get_network_request({"pageId": <pageId>, "reqid": <requestId>, "requestFilePath": "<request-path>", "responseFilePath": "<response-path>"})
```

- why_it_matters: Inspect or retain network request and response bodies while debugging a repository's web application.
- before: Retrieve the body inline by omitting `requestFilePath` and `responseFilePath`.
- sources: <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>
- gotchas: "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."

## chrome-devtools-mcp emulation supports colorScheme (chrome-devtools-mcp, 2026-01-29)
Published 2026-10-13
- slug: chrome-devtools-mcp-emulation-supports-colorscheme-2274f480ff19
- score: 0.98

How to use it:

When testing a page in light or dark mode, call `emulate` with `colorScheme` set to `"light"` or `"dark"`. Set it to `"auto"` to reset to the default.

Examples:

```
emulate({"colorScheme":"dark"})
```

- why_it_matters: Test a page's appearance under light or dark color scheme settings.
- sources: <https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.15.0>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/858>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/chrome-devtools-mcp-v0.15.0/docs/tool-reference.md>
- gotchas: "Version: 0.15.0"; "colorScheme: Enum `\"dark\"`, `\"light\"`, or `\"auto\"`; emulates dark or light mode, with `\"auto\"` resetting to default."; "Accepted colorScheme values are \"dark\", \"light\", and \"auto\"."

## chrome-devtools-mcp page navigation accepts initScript (chrome-devtools-mcp, 2026-01-29)
Published 2026-10-13
- slug: chrome-devtools-mcp-page-navigation-accepts-initscript-7dafabaa6ff2
- score: 0.97

How to use it:

When navigating to a new document, set `initScript` on `navigate_page` to run JavaScript before the page’s other scripts.

Examples:

```
navigate_page({"pageId": <pageId>, "type": "url", "url": "<url>", "initScript": "<JavaScript>"})
```

- why_it_matters: Run setup code on each new document before the page's own scripts during a navigation.
- sources: <https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.15.0>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/568>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/chrome-devtools-mcp-v0.15.0/docs/tool-reference.md>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/configuration.md>
- gotchas: "Version: 0.15.0"; "pageId (required): ID of the target page."; "initScript: JavaScript executed on each new document before other scripts for the next navigation."; "type: Navigation action; use `url` to navigate by URL."; "url: Target URL; required when `type` is `url`."; "Prerequisite: Use version 0.15.0 or later for this feature."; "Prerequisite: JavaScript evaluation must be enabled; the `--javascriptEvaluation` option defaults to true, and setting it to false disables `initScript`."; "Runs on each new document before any other scripts for the next navigation."

## chrome-devtools-mcp performance summaries include CrUX field data (chrome-devtools-mcp, 2026-02-10)
Published 2026-10-13
- slug: chrome-devtools-mcp-performance-summaries-include-crux-field-data-df8467bc1091
- score: 0.98

How to use it:

When reviewing a repository page’s performance, record a trace and inspect the stopped trace summary for CrUX field metrics alongside lab data. Set `--performance-crux=false` (or use `--no-performance-crux`) at server startup to disable sending trace URLs to the CrUX API.

Examples:

```
navigate_page({"type":"url","url":"<repository-page-url>"})
```

```
performance_start_trace({"autoStop":false,"reload":false})
```

```
performance_stop_trace({})
```

- why_it_matters: Review a performance trace for a repository page and compare lab metrics with real-user field metrics.
- sources: <https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.17.0>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/733>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/chrome-devtools-mcp-v0.17.0/docs/tool-reference.md>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/chrome-devtools-mcp-v0.17.0/README.md>
- gotchas: "Version: 0.17.0"; "autoStop (required): Whether to stop the trace automatically."; "reload (required): Whether to reload the selected page after tracing starts."; "--performanceCrux / --performance-crux: Boolean; defaults to true. Set false to disable sending URLs from performance traces to the CrUX API for field data."; "--no-performance-crux: Disable sending trace URLs to the CrUX API."; "filePath: For start/stop trace tools, path to save raw trace data; may be absolute or relative to the working directory."; "Prerequisite: Node.js v20.19 or newer maintenance LTS, Chrome current stable or newer, and npm."; "Prerequisite: Navigate to the desired URL before starting a trace if `reload` or `autoStop` is true."; "The server extracts primary navigation URLs from the trace, determined by insightSets."; "It fetches field metrics for each unique URL or origin."; "The `--performanceCrux`/`--performance-crux` boolean defaults to `true`."; "Performance tools may send trace URLs to the Google CrUX API."

## chrome-devtools-mcp adds experimental screencast recording tools (chrome-devtools-mcp, 2026-02-25)
Published 2026-10-13
- slug: chrome-devtools-mcp-adds-experimental-screencast-recording-tools-0515f8b21bdd
- score: 0.97

How to use it:

When recording a page during debugging, start chrome-devtools-mcp with `--experimentalScreencast` enabled and ffmpeg available on the server PATH. Call `screencast_start` with optional `path`, then `screencast_stop`; the stop response reports the saved path.

Examples:

```
Start the MCP server with `--experimentalScreencast`, then call `screencast_start` with `{ "path": "<output>.mp4" }` and `screencast_stop` with `{}`.
```

- why_it_matters: When recording a page during browser debugging, enable the experimental screencast tools and capture then save the recording.
- sources: <https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.18.0>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/941>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/chrome-devtools-mcp-v0.18.0/src/tools/screencast.ts>, <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/configuration.md>
- gotchas: "Version: 0.18.0"; "Availability: Experimental; enabled only when the `--experimental-screencast` command line option is provided."; "Requires Install ffmpeg and ensure it is available in the MCP server PATH."; "--experimentalScreencast / --experimental-screencast: Boolean server option; exposes the experimental screencast tools. Default is false."; "screencast_start.path: Output path; when omitted, a unique temporary path is generated. v0.18.0 records in MP4 format."; "screencast_stop parameters: No parameters."; "Prerequisite: Install ffmpeg and ensure it is available in the MCP server PATH."; "Recording is saved in mp4 format."; "If no `path` is provided, a temporary file with the correct extension is created."; "Requires ffmpeg; an error is reported if ffmpeg is not installed."; "Docs conflict: The current tool reference and current source use `filePath` and describe WebM support, while v0.18.0 source uses `path` and MP4. The v0.18.0 source was used for the version-specific tool parameters."

Next: https://sincecutoff.com/v1/changes.md?tool=chrome-devtools-mcp&score=0&cursor=eyJzY29yZSI6MCwic2VxIjozNjAsInNpbmNlIjpudWxsLCJ0b29sIjoiY2hyb21lLWRldnRvb2xzLW1jcCIsInYiOjF9
Save `next_cursor`; next visit, pass it to get only what was published since.
<!-- end of page -->