chrome-devtools-mcp 0.18.1 → 0.20.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +6 -5
- package/build/src/McpContext.js +242 -266
- package/build/src/McpPage.js +95 -0
- package/build/src/McpResponse.js +124 -48
- package/build/src/bin/chrome-devtools-cli-options.js +651 -0
- package/build/src/{cli.js → bin/chrome-devtools-mcp-cli-options.js} +12 -2
- package/build/src/bin/chrome-devtools-mcp-main.js +35 -0
- package/build/src/bin/chrome-devtools-mcp.js +21 -0
- package/build/src/bin/chrome-devtools.js +185 -0
- package/build/src/bin/cliDefinitions.js +615 -0
- package/build/src/browser.js +13 -12
- package/build/src/daemon/client.js +152 -0
- package/build/src/daemon/daemon.js +56 -17
- package/build/src/daemon/types.js +6 -0
- package/build/src/daemon/utils.js +57 -16
- package/build/src/index.js +204 -16
- package/build/src/telemetry/watchdog/ClearcutSender.js +2 -0
- package/build/src/third_party/THIRD_PARTY_NOTICES +1480 -111
- package/build/src/third_party/bundled-packages.json +4 -3
- package/build/src/third_party/devtools-formatter-worker.js +5 -14
- package/build/src/third_party/index.js +2128 -472
- package/build/src/third_party/issue-descriptions/selectivePermissionsIntervention.md +7 -0
- package/build/src/third_party/lighthouse-devtools-mcp-bundle.js +54183 -0
- package/build/src/tools/ToolDefinition.js +52 -0
- package/build/src/tools/console.js +3 -3
- package/build/src/tools/emulation.js +13 -45
- package/build/src/tools/extensions.js +17 -0
- package/build/src/tools/input.js +33 -33
- package/build/src/tools/lighthouse.js +123 -0
- package/build/src/tools/memory.js +5 -5
- package/build/src/tools/network.js +7 -7
- package/build/src/tools/pages.js +32 -32
- package/build/src/tools/performance.js +16 -14
- package/build/src/tools/screencast.js +5 -5
- package/build/src/tools/screenshot.js +6 -6
- package/build/src/tools/script.js +99 -49
- package/build/src/tools/slim/tools.js +18 -18
- package/build/src/tools/snapshot.js +5 -4
- package/build/src/tools/tools.js +2 -0
- package/build/src/types.js +6 -0
- package/build/src/utils/files.js +19 -0
- package/build/src/version.js +1 -1
- package/package.json +15 -9
- package/build/src/main.js +0 -203
package/README.md
CHANGED
|
@@ -73,7 +73,7 @@ Add the following config to your MCP client:
|
|
|
73
73
|
> [!NOTE]
|
|
74
74
|
> Using `chrome-devtools-mcp@latest` ensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.
|
|
75
75
|
|
|
76
|
-
If you are
|
|
76
|
+
If you are interested in doing only basic browser tasks, use the `--slim` mode:
|
|
77
77
|
|
|
78
78
|
```json
|
|
79
79
|
{
|
|
@@ -122,7 +122,7 @@ To use the Chrome DevTools MCP server follow the instructions from <a href="http
|
|
|
122
122
|
|
|
123
123
|
This will make the Chrome DevTools MCP server automatically connect to the browser that Antigravity is using. If you are not using port 9222, make sure to adjust accordingly.
|
|
124
124
|
|
|
125
|
-
Chrome DevTools MCP will not start the browser instance automatically using this approach
|
|
125
|
+
Chrome DevTools MCP will not start the browser instance automatically using this approach because the Chrome DevTools MCP server connects to Antigravity's built-in browser. If the browser is not already running, you have to start it first by clicking the Chrome icon at the top right corner.
|
|
126
126
|
|
|
127
127
|
</details>
|
|
128
128
|
|
|
@@ -358,7 +358,7 @@ Alternatively, follow the <a href="https://docs.qoder.com/user-guide/chat/model-
|
|
|
358
358
|
<details>
|
|
359
359
|
<summary>Qoder CLI</summary>
|
|
360
360
|
|
|
361
|
-
Install the Chrome DevTools MCP server using the Qoder CLI (<a href="https://docs.qoder.com/cli/using-cli#mcp-
|
|
361
|
+
Install the Chrome DevTools MCP server using the Qoder CLI (<a href="https://docs.qoder.com/cli/using-cli#mcp-servers">guide</a>):
|
|
362
362
|
|
|
363
363
|
**Project wide:**
|
|
364
364
|
|
|
@@ -442,9 +442,10 @@ If you run into any issues, checkout our [troubleshooting guide](./docs/troubles
|
|
|
442
442
|
- **Network** (2 tools)
|
|
443
443
|
- [`get_network_request`](docs/tool-reference.md#get_network_request)
|
|
444
444
|
- [`list_network_requests`](docs/tool-reference.md#list_network_requests)
|
|
445
|
-
- **Debugging** (
|
|
445
|
+
- **Debugging** (6 tools)
|
|
446
446
|
- [`evaluate_script`](docs/tool-reference.md#evaluate_script)
|
|
447
447
|
- [`get_console_message`](docs/tool-reference.md#get_console_message)
|
|
448
|
+
- [`lighthouse_audit`](docs/tool-reference.md#lighthouse_audit)
|
|
448
449
|
- [`list_console_messages`](docs/tool-reference.md#list_console_messages)
|
|
449
450
|
- [`take_screenshot`](docs/tool-reference.md#take_screenshot)
|
|
450
451
|
- [`take_snapshot`](docs/tool-reference.md#take_snapshot)
|
|
@@ -458,7 +459,7 @@ The Chrome DevTools MCP server supports the following configuration option:
|
|
|
458
459
|
<!-- BEGIN AUTO GENERATED OPTIONS -->
|
|
459
460
|
|
|
460
461
|
- **`--autoConnect`/ `--auto-connect`**
|
|
461
|
-
If specified, automatically connects to a browser (Chrome 144+) running
|
|
462
|
+
If specified, automatically connects to a browser (Chrome 144+) running locally from the user data directory identified by the channel param (default channel is stable). Requires the remoted debugging server to be started in the Chrome instance via chrome://inspect/#remote-debugging.
|
|
462
463
|
- **Type:** boolean
|
|
463
464
|
- **Default:** `false`
|
|
464
465
|
|