Skip to content
Open Skill · npm · MCP

Give your AI
a real Android device

Codex, Claude Code, Cursor, and Gemini can start devices, install apps, operate interfaces, and inspect screenshots through a local control plane.

View on npm →GitHub source
npm install -g droidlume-agent-control
One control path

The Skill decides, npm executes, DroidLume runs the device

There is no second macOS app and no private ADB surface. The CLI and MCP server only access a versioned loopback API.

01Agent SkillTool choice and verification
02npm CLI / MCPTyped protocol and uploads
03Control API127.0.0.1:55777
04Android 17DroidLume device runtime
23 typed tools

From device start
to screenshot proof

Agents can read tool schemas, timeouts, and error codes. Screenshots return as native MCP image content.

Devicescreate · start · stop · inspect
Appsinstall · launch · terminate
Inputtap · swipe · text · key
Proofscreenshot · diagnostics
mcp-config.json
{
  "mcpServers": {
    "droidlume": {
      "command": "npx",
      "args": ["-y",
        "droidlume-agent-control",
        "mcp"]
    }
  }
}
Built for automation

Stable identity, explicit results

01

Stable UUIDs

Targets remain clear when names or runtime serials change.

02

Streamed APKs

The client streams APK data into DroidLume for install.

03

Visual proof

Read state and use PNG captures to verify the interface.

04

Open Skill

Standard SKILL.md support for major coding agents.

FAQ

Agent Control

Do I need a GitHub ZIP?

The CLI, MCP server, and Skill are all distributed through npm.

Is this another Android emulator?

The DroidLume Mac app provides devices; Agent Control automates them.

Is it open source?

The Skill, npm CLI, MCP server, and documentation use the MIT License.

Does control traffic leave my Mac?

The control endpoint listens on 127.0.0.1 and MCP runs over local stdio.

droidlume-agent-control 1.1.1

Connect your agent in 30 seconds

Install the npm package, then choose your Agent Skill directory.

Open npm →