droidrun-agent

Control Android devices via DroidRun Portal over HTTP, WebSocket, or MCP.

9|1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/hanxi/droidrun-agent --skill droidrun-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: droidrun-agent
Source: https://github.com/hanxi/droidrun-agent/tree/main
Command: npx skills add https://github.com/hanxi/droidrun-agent --skill droidrun-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DroidRun Portal enables automation of Android device control through HTTP, WebSocket, and MCP APIs, removing manual device management friction.

Core Features & Use Cases

  • Async HTTP client (PortalHTTPClient) for HTTP server interactions with Bearer token authentication
  • Async WebSocket client (PortalWSClient) for real-time control using JSON-RPC style messages
  • MCP server for AI agent integration exposing Portal operations as MCP tools
  • PortalConfig helper for easy connection configuration
  • Supports common actions: tap, swipe, take_screenshot, input_text, get_state, get_version, and more
  • Fully asynchronous with async context managers and automatic WebSocket reconnection

Quick Start

Instantiate PortalHTTPClient or PortalWSClient with your Portal URL and token, then begin issuing commands.

Frequently Asked Questions about droidrun-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Android device control using HTTP or WebSocket?

You can automate Android device control by connecting to the DroidRun Portal using the asynchronous HTTP or WebSocket clients, authenticating with a Bearer token to issue commands like tap, swipe, or take_screenshot.

Can I integrate Android automation actions with an AI agent via MCP?

Yes, you can integrate Android automation with an AI agent by running the MCP server, which exposes DroidRun Portal operations as MCP tools for executing actions and retrieving device state.

What actions are supported for remote Android device interaction?

Supported actions for remote Android device interaction include tap, swipe, take_screenshot, input_text, get_state, and get_version across HTTP, WebSocket, and MCP transport modes.

Do I need a token to connect to the DroidRun Portal for automation?

Yes, you need a Bearer token for authentication. You configure your connection details, including the Portal URL and token, using the PortalConfig helper before issuing commands.

Does the WebSocket client for Android control handle automatic reconnection?

Yes, the asynchronous WebSocket client handles automatic reconnection and uses async context managers, ensuring persistent real-time control and reliable JSON-RPC style message delivery.

What is the best way to retrieve the current state of an Android device remotely?

The best way to retrieve the current state of an Android device remotely is to use the get_state action provided by the DroidRun Portal clients over your preferred HTTP, WebSocket, or MCP transport.