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

From the Official MCP Registry

MCP clients with registry support can discover and install Drengr directly — no manual config needed.

Claude Code
claude mcp add drengr -- npx -y drengr mcp

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

or install manually
Shell
curl -fsSL https://drengr.dev/install.sh | bash
npm
npm 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.

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
[✓] simctl (iOS)   available
[✓] Devices        1 connected
     emulator-5554 — Pixel_7
[–] Vision API key  not set

─────────────────────────────────
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.

5. LLM API Keys (Optional)

Only needed for standalone mode

If you use Drengr through an MCP client (Claude, Cursor, etc.), skip this section. The MCP client's own LLM handles all reasoning. LLM keys are only needed for drengr run, which uses its own built-in OODA agent.

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/
Config:  drengr entry removed from
         claude_desktop_config.json

Continue? [y/N] y

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

─────────────────────────────────
Drengr has been fully uninstalled.
Restart your MCP client.

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 doctorshows 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_doto interact with it. That's the core loop.