GDD - AI-Controlled Browser Farm runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 14 Oct 2026.
AI-controlled browser farm: N isolated Chromium instances with 36 MCP tools
What the code does
We read the source, 3 d 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.
var process = Process.Start(new ProcessStartInfo
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 GDD - AI-Controlled Browser Farm
same job, measured the same wayHosted MCP catalog with 30 tenant-isolated browser, RAG, AI, mail and media tools.
MCP server + Chrome extension for AI browser control with real sessions.
Control specific, already-open account-isolated Personae browser identities with MCP.
AI-powered native browser with 12 MCP tools. ~30 tokens per page.
AI browser tools with Chrome CDP. Navigate, screenshot, interact. Multi-provider failover.
262 MCP tools for agent-native control of openDAW, a browser-based DAW
Chrome automation via nodriver: 70 tools, isolated browsers, profiles and configurable startup.
Multi-session browser MCP — 15 parallel isolated browsers, 37 tools, stealth, self-improvement.
GDD - AI-Controlled Browser Farm — questions
Answers built from our own checks of this server.