chrome-devtools-mcp 0.2.2 → 0.2.3
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 +24 -0
- package/build/src/McpResponse.js +6 -1
- package/build/src/WaitForHelper.js +8 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -66,6 +66,17 @@ claude mcp add chrome-devtools npx chrome-devtools-mcp@latest
|
|
|
66
66
|
Follow https://docs.cline.bot/mcp/configuring-mcp-servers and use the config provided above.
|
|
67
67
|
</details>
|
|
68
68
|
|
|
69
|
+
<details>
|
|
70
|
+
<summary>Codex</summary>
|
|
71
|
+
Follow the <a href="https://github.com/openai/codex/blob/main/docs/advanced.md#model-context-protocol-mcp">configure MCP guide</a>
|
|
72
|
+
using the standard config from above. You can also install the Chrome DevTools MCP server using the Codex CLI:
|
|
73
|
+
|
|
74
|
+
```bash
|
|
75
|
+
codex mcp add chrome-devtools -- npx chrome-devtools-mcp@latest
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
</details>
|
|
79
|
+
|
|
69
80
|
<details>
|
|
70
81
|
<summary>Copilot / VS Code</summary>
|
|
71
82
|
Follow the MCP install <a href="https://code.visualstudio.com/docs/copilot/chat/mcp-servers#_add-an-mcp-server">guide</a>,
|
|
@@ -101,6 +112,19 @@ Go to `Cursor Settings` -> `MCP` -> `New MCP Server`. Use the config provided ab
|
|
|
101
112
|
using the standard config from above.
|
|
102
113
|
</details>
|
|
103
114
|
|
|
115
|
+
### Your first prompt
|
|
116
|
+
|
|
117
|
+
Enter the following prompt in your MCP Client to check if everything is working:
|
|
118
|
+
|
|
119
|
+
```
|
|
120
|
+
Check the performance of https://developers.chrome.com
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
Your MCP client should open the browser and record a performance trace.
|
|
124
|
+
|
|
125
|
+
> [!NOTE]
|
|
126
|
+
> 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.
|
|
127
|
+
|
|
104
128
|
## Tools
|
|
105
129
|
|
|
106
130
|
<!-- BEGIN AUTO GENERATED TOOLS -->
|
package/build/src/McpResponse.js
CHANGED
|
@@ -123,7 +123,12 @@ Call browser_handle_dialog to handle it before continuing.`);
|
|
|
123
123
|
}
|
|
124
124
|
if (this.#includeConsoleData && this.#formattedConsoleData) {
|
|
125
125
|
response.push('## Console messages');
|
|
126
|
-
|
|
126
|
+
if (this.#formattedConsoleData.length) {
|
|
127
|
+
response.push(...this.#formattedConsoleData);
|
|
128
|
+
}
|
|
129
|
+
else {
|
|
130
|
+
response.push('<no console messages found>');
|
|
131
|
+
}
|
|
127
132
|
}
|
|
128
133
|
const text = {
|
|
129
134
|
type: 'text',
|
|
@@ -110,7 +110,14 @@ export class WaitForHelper {
|
|
|
110
110
|
return;
|
|
111
111
|
})
|
|
112
112
|
.catch(error => logger(error));
|
|
113
|
-
|
|
113
|
+
try {
|
|
114
|
+
await action();
|
|
115
|
+
}
|
|
116
|
+
catch (error) {
|
|
117
|
+
// Clear up pending promises
|
|
118
|
+
this.#abortController.abort();
|
|
119
|
+
throw error;
|
|
120
|
+
}
|
|
114
121
|
try {
|
|
115
122
|
await navigationFinished;
|
|
116
123
|
// Wait for stable dom after navigation so we execute in
|