ChromeDevTools
Cursor implementation and browser console logging #545
Description of the bug
Is this supposed to work with logging the existing chrome browser instance outside cursor or the built-in browser? not working with neither of the two on my end
Reproduction
No response
Expectation
No response
MCP configuration
No response
Chrome DevTools MCP version
latest
Chrome version
No response
Coding agent version
No response
Model version
No response
Chat log
No response
Node version
No response
Operating system
None
Extra checklist
- [ ] I want to provide a PR to fix this bug
Thanks for reporting, could you please clarify the issue in more details? Are you seeing any specific error messages? The mcp server starts a separate browser instance. If you can use various configuration options to change that though https://github.com/ChromeDevTools/chrome-devtools-mcp?tab=readme-ov-file#configuration
thanks, I meant how can we use chrome-devtools-mcp in the built in cursor browser (without opening a separate browser instance)? Cursor 2.0 lets users check updates on the website we're building directly within Cursor. I have a few functions for which I’d like to view logs, but these require user credentials. Opening a separate browser instance for Cursor isn’t feasible since it would require logging in, and even if possible, it wouldn’t be an ideal approach. I’d love to hear your ideas on how to handle this with the tools we currently have.
Is there a way to make chrome-devtools-mcp interact with cursor using its own browser? The browser Cursor uses is Chrome. Thanks.
If you know the remote debugging port of the browser started by Cursor and if Cursor opens the port for the built-in browser, you can pass the --browserUrl=http://127.0.0.1:$PORT in the MCP configuration for chrome-devtools-mcp. I suspect though that the built-in browser is more like a web view in Electron? so probably it does not have a debugging port. cc @natorion
not sure but there's a button called "Toggle Chrome DevTools" that allows me to check the Elements, console logs, network logs etc. i think it's possible to work with that
thanks, I meant how can we use chrome-devtools-mcp in the built in cursor browser (without opening a separate browser instance)? Cursor 2.0 lets users check updates on the website we're building directly within Cursor. I have a few functions for which I’d like to view logs, but these require user credentials. Opening a separate browser instance for Cursor isn’t feasible since it would require logging in, and even if possible, it wouldn’t be an ideal approach. I’d love to hear your ideas on how to handle this with the tools we currently have.
Is there a way to make chrome-devtools-mcp interact with cursor using its own browser? The browser Cursor uses is Chrome. Thanks.
I would not be surprised if it has a debugging port open. Keep in mind though, that Cursor is a different browser, so you will have to log-in there with your credentials.
yeah that's not a problem since I'm already logged in the site with Cursor browser @natorion @OrKoN
We cannot connect to the Cursor browser. That browser is not Chrome, and it appears to be a implementation based on Chromium, likely a WebView within Electron. So the only viable option is to use a Chrome browser, either an instance launched by chrome-devtools-mcp or you can use the --browserUrl parameter to configure chrome-devtools-mcp to connect to a Chrome instance that you can start yourself (see for more details https://github.com/ChromeDevTools/chrome-devtools-mcp?tab=readme-ov-file#connecting-to-a-running-chrome-instance).
I opened an issue on the Cursor issue tracker: https://github.com/cursor/cursor/issues/3888 and will close this one here, as this is related to Cursor's own browser.