mirror of
https://github.com/ChromeDevTools/chrome-devtools-mcp.git
synced 2026-11-04 15:00:11 +00:00
docs: clarify Antigravity MCP setup for VS Code extension (#2855)
Clarifies MCP server configuration when using the Antigravity extension in VS Code versus standalone Antigravity IDE and VS Code Copilot. Fixes #2830.
This commit is contained in:
1 parent
47c5b3753d
commit
12e13ca455
1 file changed
+3
-1
@@ -19,7 +19,7 @@ amp mcp add chrome-devtools -- npx chrome-devtools-mcp@latest
|
||||
|
||||
To use the Chrome DevTools MCP server follow the instructions from <a href="https://antigravity.google/docs/mcp">Antigravity's docs</a> to install a custom MCP server. Add the following config to the MCP servers config:
|
||||
|
||||
```bash
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"chrome-devtools": {
|
||||
@@ -38,6 +38,8 @@ This will make the Chrome DevTools MCP server automatically connect to the brows
|
||||
|
||||
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.
|
||||
|
||||
If you are using the Antigravity extension in VS Code (instead of standalone Antigravity IDE), configure the server in Antigravity's MCP configuration (`mcp_config.json`) rather than VS Code's Copilot settings. If you do not have a browser running with remote debugging on port 9222, omit `--browser-url` to let Chrome DevTools MCP launch Chrome automatically.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
Reference in new issue
Block a user