ChromeDevTools / ChromeDevTools/chrome-devtools-mcp
The DevTools MCP is hardcoded to look for Chrome in standard locations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 52.3k
- Forks
- 4.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 83
Description
Is your feature request related to a problem? Please describe.
This seems to actually be a bug. Most people use mise or scoop for automated installation on windows. This results in chrome being installed in non standard paths.
chrome-devtools - list_pages (MCP)
⎿ Error: Could not find Google Chrome executable for channel 'stable' at:
- C:\Program Files\Google\Chrome\Application\chrome.exe,
- C:\Program Files (x86)\Google\Chrome\Application\chrome.exe,
- C:\Users\code\AppData\Local\Google\Chrome\Application\chrome.exe,
- D:\Program Files\Google\Chrome\Application\chrome.exe,
- D:\Program Files (x86)\Google\Chrome\Application\chrome.exe.
Is there a workaround for this?
Describe the solution you'd like
auto discover chrome location and use it automatically
Describe alternatives you've considered
I don't know if you have env support for this.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the Chrome executable resolution used by the chrome-devtools list_pages MCP entry point, then review how Windows installation paths are handled. Done means stable Chrome is discovered when installed through mise or scoop, including the reported nonstandard locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100