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
In addition to Chrome, Chrome DevTools MCP supports Microsoft Edge. Edge must be installed separately. It is not bundled or downloaded by the MCP server.
762
+
763
+
#### Microsoft Edge
764
+
765
+
Pass `--browser=edge` to use the Microsoft Edge browser:
Copy file name to clipboardExpand all lines: skills/chrome-devtools/SKILL.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,9 @@ description: Uses Chrome DevTools via MCP for efficient debugging, troubleshooti
5
5
6
6
## Core Concepts
7
7
8
-
**Browser lifecycle**: Browser starts automatically on first tool call using a persistent Chrome profile. Configure via CLI args in the MCP server configuration: `npx chrome-devtools-mcp@latest --help`.
8
+
**Browser lifecycle**: Browser starts automatically on first tool call using a persistent browser profile. Configure via CLI args in the MCP server configuration: `npx chrome-devtools-mcp@latest --help`.
9
+
10
+
**Browser selection**: With no browser selection arguments, stable channel Chrome browser is the default. You can use `--browser=edge` to specify the Microsoft Edge browser. You can also use `--channel=stable|beta|dev|canary` to specify a channel. Alternatively, use `--executablePath` to specify the binary path of the browser you want to use.
9
11
10
12
**Page selection**: Tools operate on the currently selected page. Use `list_pages` to see available pages, then `select_page` to switch context.
`Could not connect to Chrome in ${userDataDir}. Check if Chrome is running and remote debugging is enabled by going to chrome://inspect/#remote-debugging.`,
117
+
`Could not connect to ${browserName(browserKind)} in ${userDataDir}. Check if ${browserName(browserKind)} is running and remote debugging is enabled by going to ${inspectUrl(browserKind)}.`,
102
118
{
103
119
cause: error,
104
120
},
@@ -123,7 +139,7 @@ export async function ensureBrowserConnected(options: {
123
139
browser=awaitpuppeteer.connect(connectOptions);
124
140
}catch(err){
125
141
thrownewError(
126
-
`Could not connect to Chrome. ${autoConnect ? `Check if Chrome is running and remote debugging is enabled by going to chrome://inspect/#remote-debugging.` : `Check if Chrome is running.`}`,
142
+
`Could not connect to ${browserName(browserKind)}. ${autoConnect ? `Check if ${browserName(browserKind)} is running and remote debugging is enabled by going to ${inspectUrl(browserKind)}.` : `Check if ${browserName(browserKind)} is running.`}`,
127
143
{
128
144
cause: err,
129
145
},
@@ -137,6 +153,7 @@ interface McpLaunchOptions {
137
153
acceptInsecureCerts?: boolean;
138
154
executablePath?: string;
139
155
channel?: Channel;
156
+
browserKind?: BrowserKind;
140
157
userDataDir?: string;
141
158
headless: boolean;
142
159
isolated: boolean;
@@ -171,11 +188,18 @@ export function detectDisplay(): void {
0 commit comments