GDD MCP Server

AI-controlled browser farm: N isolated Chromium instances with 36 MCP tools

Local serverstdioPython

What is the GDD MCP server?

AI-controlled browser farm: N isolated Chromium instances with 36 MCP tools. Exposed over MCP by the gdd mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Simulate multiple real users across 22 device types — test your site like it's launch day.

  • 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
  • Human-like input — — humanize=true drives 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
  • Proxy support — — Route every browser through an upstream proxy with GDD_PROXY (with optional auth)

Its toolset

Everything the assistant can do here goes through one of these:

  • Navigation — The Navigation tool exposed by this server
  • Interaction — The Interaction tool exposed by this server
  • Emulation — The Emulation tool exposed by this server
  • 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

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at ghcr.io/cap-of-tea/gdd on a container image and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. GDD's toolset — Navigation, Interaction, Emulation and 1 more — is a fair guide to whether it matches your workflow. It is maintained by imVSmirnov; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against GDD's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the gdd mcp server does with a few real requests.

Available tools

ToolWhat it does
NavigationThe Navigation tool exposed by this server.
InteractionThe Interaction tool exposed by this server.
EmulationThe Emulation tool exposed by this server.
EditionsGDD 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.

How to install the GDD MCP server

**Linux / macOS:**

```json
{
  "mcpServers": {
    "gdd": {
      "command": "bash",
      "args": ["/path/to/Scripts/mcp-proxy.sh"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use GDD to Navigation.
  • Use GDD to Interaction.
  • Use GDD to Emulation.

Frequently asked questions

It connects GDD to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Navigation, Interaction, Emulation, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with GDD directly.