io.github.iVamsi/android-agent-kit

DroidAgentKit

Is the DroidAgentKit MCP server down? No. It is up and needs network, probed 2026-10-26.

Local-first Android development MCP: Gradle, adb, logcat, lint, crash triage, Perfetto, visuals.

needs network probed 2026-11-14 · unchanged since 2026-10-26

MCP error -32000: Connection closed
droidagent-mcp: could not find or provision a JDK 17+ runtime: getaddrinfo EAI_AGAIN github.com
Install one from https://ado

Run it: npx -y @droidagentkit/launcher@0.3.2-alpha (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/iVamsi/droid-agent-kit
Registry: active, updated 2026-10-26 · registry entry

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

SSH MCP Server io.github.hypnosis/ssh-mcp-server · alive
io.github.hypothesi/mcp-server-tauri · alive
CricketStudio MCP io.github.i-m-arul/cricketstudio-mcp · alive
agent-intercom io.github.iambashar/agent-intercom · needs env
ShipScreens MCP Server io.github.iamjamb/shipscreens · timeout
MCPBridge io.github.iamjrmh/mcpbridge · alive
io.github.iTophua/iterminal · alive
DroidAgentKit io.github.iVamsi/droidagentkit · needs network

Servers that mention android.

TVWizard ai.djwizard/tvwizard · TLS error
ai.mythex/mythex · needs auth
App Store Trends API ai.trendsapi/app-store · alive
App Store Trends MCP ai.trendsmcp/app-store · alive
HinduCalendar — panchang, festivals & muhurta app.hinducalendar/hinducalendar · alive
app.trysonar/sonar · alive
com.clauxel.aistudioandroidreleasegate/aistudioandroidreleasegate-mcp · no DNS
com.clauxel.androidcliagentgate/androidcliagentgate-mcp · no DNS

Badge for the README

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

The server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.