
GDD - AI-Controlled Browser Farm
io.github.imVSmirnovPublished by GitHub account imVSmirnovv1.5.0Updated Oct 24, 2026
AI-controlled browser farm: N isolated Chromium instances with 36 MCP tools
Overview
Runs multiple isolated Chromium browsers on your machine so an assistant can test web apps across emulated devices in parallel.
- What you can do
- GDD launches N isolated Chromium instances, each with its own profile, cookies, device emulation, geolocation and network conditions, and exposes 39 MCP tools over HTTP on localhost. Tools cover player management, navigation, interaction (tap, swipe, drag, scroll, type, press, hover, select, dialogs), reading and screenshots, emulation presets, diagnostics (console, network, performance, notifications), quick auth, JavaScript execution, and browser storage and cookies. It ships as a headless server, a desktop GUI with a live browser grid, and a Windows GUI, all exposing the same tools.
- When to use it
- Useful when you want an assistant to exercise a web app like several real users at once: multi-device responsive checks, signup and form flows, console and network error hunting, or CI-style browser runs. It fits teams already using an MCP client such as Claude Code, Cursor or a VS Code-based IDE.
- Requirements
- A local process on Windows, Linux or macOS, or the Docker image ghcr.io/cap-of-tea/gdd. The MCP endpoint is HTTP on localhost:9700 (desktop GUI on 9800); clients connect by URL or via the bundled stdio proxy scripts. Chromium downloads automatically on first launch (~80 MB). Building from source needs the .NET 8 SDK. No accounts or API keys are declared.
Installation
In SourceWeft
- Open GDD - AI-Controlled Browser Farm in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
GDD — Giggly-Dazzling-Duckling
AI-controlled browser farm on your machine
Simulate multiple real users across 22 device types — test your site like it's launch day.
[Release] [Platforms] [MCP] [MCP Registry] [License]
How It Works
You: Open 3 iPhones and a desktop, navigate to myapp.com, test the signup form on all devices
Claude Code creates 4 browsers with device emulation, navigates each to your app, fills in the form, takes screenshots, checks console for errors — all in parallel.
GDD runs N isolated Chromium instances, each with its own profile, cookies, device emulation, geolocation, and network conditions. It exposes 39 MCP tools via HTTP on localhost:9700.
[GDD Video Wall — 3 devices testing simultaneously]
Install
GDD comes in two flavours. The Server is headless — it's just the MCP backend, runs anywhere (including boxes with no display), and is all you need for pure AI automation. The Desktop app adds a GUI: a live grid of browser thumbnails you can click into to take over a session by hand. The Server runs on port 9700, the Desktop app on 9800 — so you can run both side by side.
Server (headless) — the MCP backend:
Desktop app (GUI) — a live grid of browser thumbnails you can click into:
The Windows app uses WebView2; the Linux/macOS app (built with Avalonia) drives real Chromium windows parked off-screen. Self-contained binary, ~70 MB. No .NET installation needed. Chromium downloads automatically on first launch.
One-liner (Linux):
Docker
The Docker image runs in headless mode with all Chromium dependencies pre-installed.
By default, browsers launch in headed mode (visible windows). Add --headless for CI/CD. Other flags: --stealth and --stealth-max for anti-bot masking, --update to self-update, --version and --help. The Configuration section below lists every flag and environment variable.
Connect to Your AI Client
Add to .mcp.json and restart your AI client:
That's it. Start GDD, tell Claude or Cursor to test your app.
Claude Desktop users: Download the
.mcpbfile from Releases and open it — GDD installs as a one-click desktop extension. No manual config needed.
Config file locations
Global and project configs are merged — servers from both are available simultaneously. Changes are picked up only when restarting the AI client session.
VS Code-based IDEs (Windsurf, Antigravity, Copilot)
VS Code-based IDEs use a different config format than Claude Code / Cursor.
Project config — .vscode/mcp.json:
Global config — open via Cmd+Shift+P → "Open User Settings (JSON)":
Global settings.json location: macOS — ~/Library/Application Support/<IDE>/User/settings.json, Linux — ~/.config/<IDE>/User/settings.json, Windows — %APPDATA%/<IDE>/User/settings.json. Replace <IDE> with your editor name (Code, Windsurf, Antigravity, etc.).
stdio-proxy alternative (.vscode/mcp.json):
Permissions (Claude Code)
By default, Claude Code asks for confirmation on every MCP tool call. To allow GDD tools without prompts, add to ~/.claude/settings.json:
This single wildcard covers all 39 GDD tools. Restart Claude Code after editing.
Auto-launch via stdio proxy (alternative)
Proxy scripts start GDD automatically when your AI client connects:
Windows:
Linux / macOS:
Add "--headless" to the args array for CI/CD.
Tip: On first launch, GDD downloads Chromium (~80 MB). If your AI client times out, run GDD manually first, then reconnect.
Autostart as service (macOS / Linux)
macOS (launchd):
Manage: launchctl list | grep gdd / bash Scripts/install-launchd.sh --uninstall
Linux (systemd):
Direct HTTP (without AI client)
GDD uses standard JSON-RPC 2.0 — works with curl, Python, Node.js, or any HTTP client.
Features
- Multi-device — Run N isolated Chromium instances with 22 device presets (phones, tablets, desktops)
- AI-native — 39 MCP tools for Claude Code, Cursor, or any MCP-compatible client
- Cross-platform — Native GUI with a live video wall on Windows, Linux & macOS, plus a headless server for CI/CD
- Full interaction — Navigate, tap, type, press keys and shortcuts, drag, swipe, scroll, hover, handle dialogs, take screenshots
- Real keyboard — Typing sends genuine, trusted keystrokes (the full keydown→input chain), so input masks, autocomplete and
maxlengthbehave exactly as they do for a real user, and rich-text (contenteditable) editors work;gdd_presshandles single keys and shortcuts like Enter, Tab, Escape and Ctrl+A - Physical keyboard layouts — Keystrokes carry the real
code/keyCodeof the emulated locale's keyboard: Russian ЙЦУКЕН puts «а» on the physicalKeyF, French AZERTY and German QWERTZ remap their keys, dead-key accents and AltGr symbols work. The layout followsgdd_set_languageautomatically (US, RU, DE, FR) - Human-like input —
humanize=truedrives a continuous cursor path (cubic Bézier with easing and micro-jitter) that carries over between clicks, hovers and drags; taps fire a single device-appropriate input (touch or mouse), never both - Anti-bot stealth — opt-in
--stealthmasks the usual automation tells (navigator.webdriver, etc.);--stealth-maxadds headless/datacenter evasions (coherent user-agent client hints, a plausible WebGL vendor, realistic device metrics) — on a headless container this halved CreepJS's headless score - Proxy support — Route every browser through an upstream proxy with
GDD_PROXY(with optional auth) - Header rewriting —
gdd_set_headerscan stripX-Frame-Options/CSPframe-ancestorsto load a site in an iframe, or add/replace response headers - Device emulation — Screen size, DPR, touch, user agent, geolocation, timezone, language
- Network control — Simulate 4G, Fast 3G, Slow 3G, or offline per browser
- Diagnostics — Console errors, network traffic, performance metrics, push notifications
- Error beacon — Every tool response warns about JS errors across all browsers automatically
- Docker-ready — Official image on GHCR (
ghcr.io/cap-of-tea/gdd), listed on the MCP Registry - Self-updating — Built-in version check and one-command update
MCP Tools (39)
Player Management
Navigation
Interaction
Reading & Screenshots
Emulation
State & Diagnostics
Auth & Execution
Browser Storage
Help & Updates
Device Presets (22)
Phones (11)
Tablets (6)
Desktops (5)
Architecture
Editions
GDD ships as three apps over one shared core. The two GUIs differ only in the desktop toolkit (WebView2 on Windows, Avalonia on Linux/macOS); all three expose the same 39 MCP tools.
Tech Stack
Project Structure
Configuration
appsettings.json next to the executable:
Command-line flags
Environment variables
Handy for Docker and CI, where an appsettings.json file is awkward:
Documentation
- GDD-MANUAL.md — Full usage manual with workflow examples
- GDD-ARCHITECTURE.md — Architecture deep-dive
- GDD-PROMPT.md — Claude agent instructions for MCP integration
- docker-compose.prod.yml — Self-host GDD as a remote MCP server behind a Caddy bearer-token proxy
- CONTRIBUTING.md — Contribution guidelines
Privacy
Privacy Policy
GDD runs entirely on your local machine. No telemetry, no analytics, no data collection.
- No data leaves your machine — all browser profiles, screenshots, logs, and cookies stay in local storage
- Browser profiles — stored in
%LOCALAPPDATA%\GDD\Profiles(Windows) or~/.local/share/GDD/Profiles(Linux/macOS) - No third-party services — GDD does not contact any external APIs except GitHub Releases for optional update checks
- Update checks —
gdd_check_updatemakes a single read-only request toapi.github.com. Opt out by not calling the tool, or setCheckForUpdates: falseinappsettings.json - MCP server — listens on
localhostonly (default port 9700), never exposed to the network
Contact: [email protected]
License
imVS©, free for personal use.
Source Available — Non-Commercial. Free for personal use, education, and research. Commercial use requires a paid license. See LICENSE for full terms.
Commercial licensing: [email protected]
Source: README.md at commit 12a4e4f
Tools
0Version history
1- v1.5.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.