|
|
|
|
|
by wraptile
259 days ago
|
|
Most browsers these days expose a control API (like ChromeDevtools Protocol MCP [1]) that open up a socket API and can take in json instructions for bidirectional communication. Chrome is the gold standard here but both Safari and Firefox have their own driver. For you existing browser session you'd have to start it already with open socket connection as by default that's not enabled but once you do the server should able to find an open local socket and connect to it and execute controls. worth nothing that this "control browser" hype is quite deceiving and it doesn't really work well imo because LLMs still suck at understanding the DOM so you need various tricks to optimize for that so I would take OP's claims with a giant bag of salt. Also these automations are really easy to identify and block as they are not organic inputs so the actual use is very limited. - https://github.com/ChromeDevTools/chrome-devtools-mcp/ |
|