Getting Started

Drengr installs in under a minute. It auto-detects your device tools, so in most cases you just install and go.

1. Install Drengr

Pick whichever method you prefer. Both install the same single binary.

Shellcurl -fsSL https://drengr.dev/install.sh | bash
npmnpm install -g drengr

Supported: macOS (Apple Silicon & Intel), Linux (x64 & ARM64).

The shell installer downloads a prebuilt binary to /usr/local/bin and verifies its SHA256 checksum.

MCP Registry

Drengr is listed on the Official MCP Registry. MCP clients with registry support can discover and install it directly — no manual config needed.

Claude Codeclaude mcp add-from-registry dev.drengr/server

For other clients, search "Drengr" in your MCP client's server browser or add the registry identifier: dev.drengr/server

2. Verify

Run the health check. It tells you exactly what's working and what needs fixing.

drengr doctor
  Drengr Doctor
  ─────────────────────────────────────────────

  [✓] ADB                    /usr/local/bin/adb (1.0.41)
  [✓] simctl (iOS)           available (/usr/bin/xcrun)
  [✓] Devices                1 connected
       emulator-5554 — Pixel_7 (Android 14)
  [–] Vision API key         not set (only needed for drengr run)

  ─────────────────────────────────────────────
  Status: READY for MCP mode

  → Next:  drengr setup

If ADB or simctl shows [✗], see the device tools section below. Drengr will tell you exactly what to do.

3. Connect to Your MCP Client

Drengr auto-generates the config for your MCP client.

drengr setup

This detects your platform and prints the JSON config you need. You can also write it directly:

drengr setup --client claude-desktop --write
drengr setup --client cursor --write
drengr setup --client claude-code --write
drengr setup --client windsurf --write
drengr setup --client vscode --write

After writing the config, restart your MCP client to pick up the changes.

4. Device Tools

You probably don't need to do anything here.

Drengr auto-detects ADB and Xcode from your shell profile, even inside MCP clients that don't inherit your PATH. If drengr doctor shows green checks, skip this section entirely.

Uninstall

Removes the binary, all local data (~/.drengr/), and cleans up your MCP client configs. Leaves nothing behind.

drengr uninstall
  Drengr Uninstall
  ─────────────────────────────────────────────

  The following will be removed:

  Binary:     /usr/local/bin/drengr
  Data:       ~/.drengr/  (logs, sessions, screen maps)
  MCP config: drengr entry will be removed from:
              ~/Library/Application Support/Claude/claude_desktop_config.json

  Continue? [y/N] y

  ✓ Cleaned MCP config: .../claude_desktop_config.json
  ✓ Removed ~/.drengr/
  ✓ Removed /usr/local/bin/drengr

  ─────────────────────────────────────────────
  Drengr has been fully uninstalled.
  Restart your MCP client to apply config changes.

If you installed via npm, drengr uninstall cleans up data and MCP configs, then reminds you to run npm uninstall -g drengr to remove the npm wrapper.

What's Next

Once drengr doctor shows green and you've connected your MCP client, you're ready. Ask your AI agent:

"Use drengr to take a screenshot of the device."

The agent will call drengr_look to see the screen, then drengr_do to interact with it. That's the core loop.