toggldev-remote

Control your Android Developer Options from the terminal — or let your AI agent do it.

CLI and MCP server that discovers, pairs with, and controls the Developer options on Android device over your local network. No USB cable, no manual tapping through menus.

📱 Companion TogglDev app: Available on Google Play and Github

Install

npm install -g toggldev-remote

This installs two commands:

Command	Purpose
toggldev	CLI for direct terminal use
toggldev-mcp	MCP server for AI clients

---

The Problem

You're deep in a coding session. You need wireless debugging enabled on your phone, or you need to change animation scales for testing. So you pick up the phone, unlock it, navigate to Developer Options, toggle the setting, then get back to your terminal.

With an AI agent, it's worse — the agent can build your app, but it can't reach over and flip a switch on your phone.

The Fix

Via Terminal:

toggldev toggle --key adb_wifi_enabled --enabled true

Via AI Agent (MCP):

"Enable wireless debugging"

One command, or one prompt to your AI — no human in the loop.

---

Features

• Auto-discovery — Finds devices running TogglDev on the local network via mDNS. No IP addresses to remember.
• Secure pairing — Connects using the 6-digit pairing code from the TogglDev app. Credentials are saved for future sessions.
• Full control — Toggle developer settings, set animation scales, get device status, retrieve wireless debugging connection info.
• MCP server — Works as a tool provider for Claude, Cursor, Gemini, and any MCP-compatible AI agent.
• Remote access — Pair over Tailscale to control your device from any network.

---

Prerequisites

• Node.js (v18+)
• TogglDev Android App v2.0+ — available on Google Play or GitHub Releases
• Your computer and Android device on the same local network (or connected via Tailscale)

---

Quick Start

# 1. Find your phone on the network
toggldev discover

# 2. Open the TogglDev app, note the 6-digit code, then pair
toggldev pair --host 192.168.1.100 --port 8734 --code 123456

# 3. Enable wireless debugging
toggldev toggle --key adb_wifi_enabled --enabled true

# 4. Get the ADB connection info
toggldev wireless-debug-info

# 5. Connect ADB
adb connect <ip>:<port>

---

CLI Reference

Discover devices

toggldev discover
toggldev discover --timeout 10

Pair with a device

toggldev pair --host <ip> --port <port> --code <code>

Saves authentication to ~/.toggldev/config.json.

Get device status

toggldev status

Toggle a setting

toggldev toggle --key adb_wifi_enabled --enabled true

Set a setting value

toggldev set --key window_animation_scale --value 0.5

Get wireless debugging info

toggldev wireless-debug-info

---

AI Agent Setup (MCP)

Use toggldev-remote as a tool provider for any MCP-compatible AI assistant.

Claude Code

claude mcp add toggldev toggldev-mcp

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "toggldev": {
      "command": "toggldev-mcp",
      "args": []
    }
  }
}

Cursor IDE

1. Settings > Features > MCP
2. + Add New MCP Server
3. Type: command, Command: toggldev-mcp

Gemini CLI / Other MCP Clients

Point your MCP configuration to:

toggldev-mcp

---

MCP Tools

Tool	Description
discover_devices	Find TogglDev instances on the local network
pair_device	Pair with a device using host, port, and pairing code
get_status	Get current developer options status
toggle_setting	Toggle a boolean setting (e.g. adb_wifi_enabled)
set_setting	Set a value for a setting (e.g. window_animation_scale to 0.5)
get_wireless_debug_info	Get IP and port for wireless ADB connection

---

Remote Access

By default, discovery and control work over the local network. To control your device from anywhere:

1. Install Tailscale on your PC and Android phone
2. Sign in on both with the same account
3. Note your phone's Tailscale IP (usually 100.x.x.x)
4. Pair using that IP:

   toggldev pair --host 100.x.x.x --port 8734 --code <code>

Once paired, all commands work from any network. The Tailscale IP stays stable across network changes.

Note: toggldev discover uses mDNS, which doesn't work over Tailscale. Use the Tailscale IP directly for pairing.