You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add update notification to both binaries (#1783)
Both `chrome-devtools` and `chrome-devtools-mcp` now log a notification
when a newer version is detected to be available.
This detection is implemented as follows:
1. Read the latest version from a local 24-hour cache
(`~/.cache/chrome-devtools-mcp/latest.json`).
2. If the cache is stale or missing, spawn a detached background process
to fetch the latest version from the npm registry and update the cache
file.
Copy file name to clipboardExpand all lines: README.md
+18-12Lines changed: 18 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,12 @@ Google handles this data in accordance with the [Google Privacy Policy](https://
51
51
52
52
Google's collection of usage statistics for Chrome DevTools MCP is independent from the Chrome browser's usage statistics. Opting out of Chrome metrics does not automatically opt you out of this tool, and vice-versa.
53
53
54
-
Collection is disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.
54
+
Collection is disabled if `CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS` or `CI` env variables are set.
55
+
56
+
## Update checks
57
+
58
+
By default, the server periodically checks the npm registry for updates and logs a notification when a newer version is available.
59
+
You can disable these update checks by setting the `CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS` environment variable.
55
60
56
61
## Requirements
57
62
@@ -74,7 +79,7 @@ Add the following config to your MCP client:
74
79
}
75
80
```
76
81
77
-
> [!NOTE]
82
+
> [!NOTE]
78
83
> Using `chrome-devtools-mcp@latest` ensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.
79
84
80
85
If you are interested in doing only basic browser tasks, use the `--slim` mode:
@@ -143,7 +148,7 @@ claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest
143
148
144
149
**Install as a Plugin (MCP + Skills)**
145
150
146
-
> [!NOTE]
151
+
> [!NOTE]
147
152
> If you already had Chrome DevTools MCP installed previously for Claude Code, make sure to remove it first from your installation and configuration files.
148
153
149
154
To install Chrome DevTools MCP with skills, add the marketplace registry in Claude Code:
@@ -200,7 +205,7 @@ startup_timeout_ms = 20_000
200
205
201
206
<details>
202
207
<summary>Command Code</summary>
203
-
208
+
204
209
Use the Command Code CLI to add the Chrome DevTools MCP server (<ahref="https://commandcode.ai/docs/mcp">MCP guide</a>):
[<imgsrc="https://img.shields.io/badge/Visual_Studio-Install-C16FDE?logo=visualstudio&logoColor=white"alt="Install in Visual Studio">](https://vs-open.link/mcp-install?%7B%22name%22%3A%22chrome-devtools%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22chrome-devtools-mcp%40latest%22%5D%7D)
425
+
426
+
**Click the button to install:**
427
+
428
+
[<imgsrc="https://img.shields.io/badge/Visual_Studio-Install-C16FDE?logo=visualstudio&logoColor=white"alt="Install in Visual Studio">](https://vs-open.link/mcp-install?%7B%22name%22%3A%22chrome-devtools%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22chrome-devtools-mcp%40latest%22%5D%7D)
429
+
424
430
</details>
425
431
426
432
<details>
@@ -446,7 +452,7 @@ Check the performance of https://developers.chrome.com
446
452
447
453
Your MCP client should open the browser and record a performance trace.
448
454
449
-
> [!NOTE]
455
+
> [!NOTE]
450
456
> The MCP server will start the browser automatically once the MCP client uses a tool that requires a running browser instance. Connecting to the Chrome DevTools MCP server on its own will not automatically start the browser.
451
457
452
458
## Tools
@@ -591,7 +597,7 @@ The Chrome DevTools MCP server supports the following configuration option:
591
597
-**Default:**`true`
592
598
593
599
-**`--usageStatistics`/ `--usage-statistics`**
594
-
Set to false to opt-out of usage statistics collection. Google collects usage data to improve the tool, handled under the Google Privacy Policy (https://policies.google.com/privacy). This is independent from Chrome browser metrics. Disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.
600
+
Set to false to opt-out of usage statistics collection. Google collects usage data to improve the tool, handled under the Google Privacy Policy (https://policies.google.com/privacy). This is independent from Chrome browser metrics. Disabled if `CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS` or `CI` env variables are set.
595
601
-**Type:** boolean
596
602
-**Default:**`true`
597
603
@@ -705,7 +711,7 @@ Make sure your browser is running. Open gemini-cli and run the following prompt:
705
711
Check the performance of https://developers.chrome.com
706
712
```
707
713
708
-
> [!NOTE]
714
+
> [!NOTE]
709
715
> The <code>autoConnect</code> option requires the user to start Chrome. If the user has multiple active profiles, the MCP server will connect to the default profile (as determined by Chrome). The MCP server has access to all open windows for the selected profile.
710
716
711
717
The Chrome DevTools MCP server will try to connect to your running Chrome
@@ -741,7 +747,7 @@ Add the `--browser-url` option to your MCP client configuration. The value of th
741
747
742
748
**Step 2: Start the Chrome browser**
743
749
744
-
> [!WARNING]
750
+
> [!WARNING]
745
751
> Enabling the remote debugging port opens up a debugging port on the running browser instance. Any application on your machine can connect to this port and control the browser. Make sure that you are not browsing any sensitive websites while the debugging port is open.
746
752
747
753
Start the Chrome browser with the remote debugging port enabled. Make sure to close any running Chrome instances before starting a new one with the debugging port enabled. The port number you choose must be the same as the one you specified in the `--browser-url` option in your MCP client configuration.
Copy file name to clipboardExpand all lines: src/bin/chrome-devtools-mcp-cli-options.ts
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -233,7 +233,7 @@ export const cliOptions = {
233
233
type: 'boolean',
234
234
default: true,
235
235
describe:
236
-
'Set to false to opt-out of usage statistics collection. Google collects usage data to improve the tool, handled under the Google Privacy Policy (https://policies.google.com/privacy). This is independent from Chrome browser metrics. Disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.',
236
+
'Set to false to opt-out of usage statistics collection. Google collects usage data to improve the tool, handled under the Google Privacy Policy (https://policies.google.com/privacy). This is independent from Chrome browser metrics. Disabled if `CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS` or `CI` env variables are set.',
0 commit comments