A little while ago I wrote an MCP server that lets an AI agent inspect and control Firefox through the Remote Debugging Protocol. It got adopted into the Mozilla org. That's a nice flex, and I'll take it, but it buries the more useful story, which is why I built it. It wasn't to give my agent a browser. It was to make my agent write its own tests.
The real problem: e2e tests, not browsing
Multi-agent orchestration I've mostly got a handle on. My actual pain, the thing that eats my evenings, is end-to-end testing. Nobody wants to write it, it rots the moment the UI shifts, and it's exactly the kind of mechanical-but-fiddly work you'd love to hand off.
So the flow I actually care about looks like this:
Claude has a "test skill" that tells it to click through the app using the Firefox MCP: open the page, fill the form, follow the flow, read the DOM back.
