CommunityStale· 5mo★ 4.3by hyperb1iss

DroidMind

Controls Android devices via ADB for device control, debugging, system analysis, and UI automation with a security framework.

View repo

Safety & Trust

Delv Safety Grade: C

Score 58/100 · assessed 2026-04-18

Maintainer55

Permissions25

Supply chain35

Transparency75

Incidents100

DroidMind is a solo-maintained MCP server that exposes Android Debug Bridge (ADB) capabilities to Claude. The maintainer (hyperb1iss) appears active with reasonable GitHub presence, but this is a single-person project with limited community review. The permissions surface is substantial: full device control including app installation, file system access, shell command execution, UI automation, and screenshot capture. Installation requires cloning from git and using uvx, bypassing standard package registries entirely, which removes supply chain protections like versioning and integrity checks. The repository is open source with adequate documentation, though it's relatively new. No security incidents are known. The core risk is the breadth of device control combined with direct ADB access, which effectively grants shell-level privileges on any connected Android device. Appropriate for developers who understand ADB security implications and trust their device connections.

Green flags

Open source with clear documentation and examples
Active repository with recent commits and maintenance
Explicit security framework mentioned in description
Scoped to ADB protocol, not arbitrary system access
No environment secrets required for basic operation

Red flags

Full shell execution on connected Android devices via ADB
No package registry distribution, git-only install bypasses verification
Solo maintainer with limited bus factor for security updates
Broad device control surface: apps, files, UI, system settings
Direct hardware access (screenshots, input simulation, system state)

Permissions requested

Shell executeRead filesWrite filesOutbound networkDesktop control

Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

uvx --from git+https://github.com/hyperb1iss/droidmind droidmind

Review

DroidMind is an MCP server that bridges Claude to Android devices through ADB. It gives you programmatic control over phones and tablets: install apps, pull logs, capture screenshots, simulate taps and swipes, query system state. If you're testing Android apps or debugging device behaviour, this is the kind of tooling that saves you from switching contexts constantly. I'd reach for this when I'm triaging a bug report that requires device state inspection. Instead of manually running adb commands and copying output into Claude, I can ask for logcat snippets, package info, or battery stats in plain English. The UI automation is particularly useful for repetitive test flows: you can script tap sequences, verify screen content, and pull screenshots without writing Appium boilerplate. The security framework means you can restrict which commands Claude can run, which matters if you're exposing this to less technical team members. The install is straightforward if you already have ADB configured. You'll need the Android SDK platform tools in your PATH and a device connected via USB or network. Once that's sorted, uvx pulls the server from the repo and you add a single config block to Claude Desktop. The first time you run a command, you'll authorise the connection on the device itself. Quirks: this is a power tool, not a hand-holding wizard. If you don't know what ADB is or haven't used it before, you'll spend more time learning ADB than benefiting from the MCP layer. The security framework is opt-in, so you need to configure it explicitly if you want guardrails. Documentation assumes familiarity with Android debugging workflows. There's no graphical device picker, so if you have multiple devices connected, you'll need to specify which one via ADB's own device selection. Skip this if you're not already doing Android development or QA. It's built for people who live in adb shell and want to automate the repetitive bits. If you're just curious about Android automation, start with the Android SDK docs first, then come back here when you're tired of typing the same commands.

Verdict

Install this if you're debugging Android apps or running device-based QA workflows and you're comfortable with ADB. Skip it if you've never used Android Developer Tools or don't have a testing device to hand. It's a specialist tool that does one thing well for a specific audience.

Good at

Turns repetitive ADB commands into natural language requests, saving context switches during debugging.
UI automation without Appium overhead: script taps, swipes, and assertions directly through Claude.
Security framework lets you restrict which commands are allowed, useful for shared or team environments.
Pulls device state (logs, battery, packages) into Claude's context without manual copy-paste.
Works over USB or network ADB, so you can debug remote devices or emulators.

Watch out

Assumes you already know ADB. If you don't, the learning curve is steep and not covered here.
Security restrictions are opt-in, so you need to configure them yourself if you want guardrails.
Multi-device setups require manual ADB device selection, no built-in picker.
Documentation is sparse on edge cases like emulator quirks or wireless debugging gotchas.
Only useful if you have an Android device or emulator to test against.

Use cases

Android app testing
device log inspection
UI automation
on-device debugging

Getting started

1. Install Android SDK platform tools and ensure `adb devices` lists your connected device. 2. Run `uvx --from git+https://github.com/hyperb1iss/droidmind droidmind` to install the server. 3. Add the server config to your Claude Desktop settings (check the repo README for the exact JSON block). 4. Restart Claude Desktop and ask it to list installed packages on your device to verify the connection. 5. Watch out: if you have multiple devices connected, ADB will complain. Disconnect extras or specify a device serial in your ADB environment.

Works with

Claude DesktopClaude CodeCursor