3 ms·
Interesting, thanks To your opinion, what's the benefits compared to the native Chrome remote debugging feature + the chrome-devtools MCP?
by LollipopYakuza 8mo ago
Interesting, thanks
To your opinion, what's the benefits compared to the native Chrome remote debugging feature + the chrome-devtools MCP?
- infamia 8mo agoMCP eats lots of context (~20k tokens for chrome's). The more tokens you use needlessly, the faster your context rots (i.e., worse performance).
- xmorse 8mo agoThis one works as an extension so you don't need a new browser specifically for agents. It's easier to collaborate. Also if you run the MCP in non headless mode it brings to front the browser on every interaction, like opening a new page. With the extension this does not happen. Another benefit is context usage. The cli can also do a lot more than other MCPs because it uses code snippets run in a stateful sandbox to control the browser, so it can do virtually anything instead of just a few exposed tools like `scroll`, `click`