| ▲ | badlogic 13 hours ago | |
Neat. Any reason why the MCP server doesn't expose a JavaScript/eval tool? Current models excel at writing JS to drive and inspect the DOM. They aren't great at driving browsers via screenshots. | ||
| ▲ | hugs 13 hours ago | parent | next [-] | |
> why the MCP server doesn't expose a JavaScript/eval tool? no reason other than my number #1 goal was "ship something". i only started the actual coding on dec 11. it's been a bit of a sprint the last two weeks! though "image-based" vs "dom-based" testing approaches is a very big topic! (look forward to researching that more in the future.) v1 announcement: https://github.com/VibiumDev/vibium/blob/main/docs/updates/2... | ||
| ▲ | coty 12 hours ago | parent | prev [-] | |
FWIW, if you have Claude Code or the like, you can quickly prompt your way to an eval function in MCP. It already exists in clicker and the client API. You can use it to get the accessibility tree, for example, and use that to find what to fill out and click. | ||