Skip to content

docs: update auto connect docs to mention min Chrome version #681

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
OrKoN merged 1 commit into from
Dec 16, 2025
Merged

docs: update auto connect docs to mention min Chrome version #681

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 3 additions & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -499,7 +499,7 @@ In these cases, start Chrome first and let the Chrome DevTools MCP server connec

**Step 1:** Set up remote debugging in Chrome

In Chrome, do the following to set up remote debugging:
In Chrome (\>= M144), do the following to set up remote debugging:

1. Navigate to `chrome://inspect/#remote-debugging` to enable remote debugging.
2. Follow the dialog UI to allow or disallow incoming debugging connections.
Expand All @@ -516,17 +516,13 @@ The following code snippet is an example configuration for gemini-cli:
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"chrome-devtools-mcp@latest",
"--autoConnect",
"--channel=canary"
]
"args": ["chrome-devtools-mcp@latest", "--autoConnect", "--channel=beta"]
}
}
}
```

Note: you have to specify `--channel=canary` until Chrome M144 has reached the
Note: you have to specify `--channel=beta` until Chrome M144 has reached the
stable channel.

**Step 3:** Test your setup
Expand Down