agent-browser or mare-browser? Here's how I actually choose.
If you're building web apps with an AI agent, you hit the same wall pretty fast: the model can write the code, but it can't see what the code does in a real browser. It can't click the button, watch the login fail, read the console error, or check what the API actually returned. It's coding blind.
That's what browser automation fixes. You give the agent a real browser it can drive — open a page, fill a form, click around, read the DOM, watch the network — so the loop stops being "AI writes code, you test it, you describe the bug, AI guesses" and becomes "AI writes code, AI tests it, AI reads the failure, AI fixes it." For both developing and testing, that's the difference between an assistant and an actual pair.
The way you wire that up is an MCP server — a small program that exposes browser actions as tools your agent can call. Both tools in this post are exactly that:
agent-browser is Vercel's browser automation tool for agents — a fast native CLI with a huge feature set and an MCP mode. Think "do almost anything in a browser, anywhere."
