browser-tools-mcp

Why a new browser extension for Chrome instead of an MCP operating Chrome over Chrome DevTools Protocol? https://chromedevtools.github.io/devtools-protocol/ Not vouching for this project, but just an example of the category existing: https://github.com/AgentDeskAI/browser-tools-mcp

Thanks for the detailed write-up, this is super useful! I really appreciate it. > Claude captures all the NPM commands from the package json into the instructional file Oh neat, I didn't know that. I'll try to use `/init` next time! > it kept trying to run `npm run dev` which spins up the app itself. That's... not ideal since I'm running it myself so it can hot-reload +1 I regularly notice that behaviour too. I'm running node in dev mode, then Cursor wants to run node, but the port is already in use. > I'd be curious about is if there is a "clientside browser" MCP Great point, I noticed this is a common feature request for front-end development. I haven't used it myself, but multiple people mentioned BrowserTools [1]. I think it can read the Dev Tools console, but I'm not sure about multimodal or access to the DOM. [1]: https://github.com