
DroidAgentKit
io.github.iVamsiPublished by GitHub account iVamsiv0.2.6-alphaUpdated Oct 24, 2026
Local-first Android development MCP: Gradle, adb, logcat, lint, crash triage, Perfetto, visuals.
The publisher's own server: droid.monster — specs
Overview
A local MCP server that gives AI coding agents structured Android tooling: Gradle tasks, adb, logcat, lint, crash triage, Perfetto traces and visual diffs.
- What you can do
- Inspect Android projects and run allowlisted Gradle tasks, tests and builds, with build diagnosis and APK size analysis by default (core group). Manage devices: list devices, install and launch apps, capture logcat and screenshots, take accessibility snapshots and look up UI elements. Run lint, crash triage with R8 de-obfuscation, dependency checks and build performance reports. Optional groups add device diagnostics, bounded device control with tap-by-label and flow recording, Perfetto trace analysis, pixel-diff visual regression, read-only app storage inspection and experimental emulator network capture.
- When to use it
- Use it when an agent works on Android projects and you want it to build, test, debug and profile through structured tools instead of raw shell access. It suits crash triage, logcat analysis, APK size questions and Compose visual regression, and is not for iOS work.
- Requirements
- Local process started via the npm launcher package with npx; Node 18+ is needed at install time. A JDK 17+ on PATH, in JAVA_HOME or named by DROIDAGENT_JAVA, otherwise a verified Temurin JRE is downloaded and cached. Optional adb/platform-tools with ANDROID_HOME or adbPath configured for device tools. A project config file tunes allowlists and capabilities.
Installation
In SourceWeft
- Open DroidAgentKit in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.2.6-alphaLatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
Other Droid integrations
droid.monster — specs
monster.droidOfficial publisher
A remote MCP server for looking up sourced specifications of commercial robots, comparing models, and finding compatible spare parts.
CodeDroid
Published by GitHub account codedroid-team
Lets an MCP client drive your real Android phone: read the screen, tap, type, swipe, take screenshots, install APKs and run adb commands.

ZennoDroid: tasks
com.zennolab
Local Windows MCP server that lets an assistant create, configure, start and monitor ZennoDroid automation tasks and their sessions.

ZennoDroid: ProjectMaker
com.zennolab
Connects an AI assistant to ZennoDroid ProjectMaker so it can read and edit the open project, run it, and record actions.

ZennoDroid: devices of running tasks
com.zennolab
ZennoLab sidecar that lets an assistant inspect and drive the Android devices of running ZennoDroid tasks: screen, elements, apps and gestures.