agent-in-browser runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 24 Oct 2026.
Real browser for any agent: Chrome/Edge/Brave via CDP, Firefox via BiDi. Refs, forms, console, net.
What the code does
We read the source, 23 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
return filepath.Join(append([]string{h}, p...)...)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to agent-in-browser
same job, measured the same way220 browser automation tools for Chrome, Edge, and Firefox via CDP + BiDi. 100% Python.
Debug bridge inside your web app: an agent reads the DOM, console and network. Any browser.
Drive your real, logged-in Chrome from any AI agent - 40 tools. Needs our Chrome extension too.
Stealth browser automation for AI agents — real Chrome, N parallel persistent logged-in sessions.
Drive your real, logged-in Chrome/Edge from AI agents over CDP. Faster. Sharper.
Read-only MCP server for browser bookmarks: Chrome, Safari, Firefox, and read-later exports.
MCP server + Chrome extension for AI browser control with real sessions.
Browser control + session recording MCP for AI coding agents (Claude Code, Cursor) — real Chrome.
agent-in-browser — questions
Answers built from our own checks of this server.