About アイリ Android
アイリ Android is an MCP server that lets LLMs control Android devices, and is a child project of airi. It provides tools for input, device information, UI inspection, and device management.
Key features
- 01Tap, swipe, and enter text
- 02Send key events and press actions
- 03Read screen size and display density
- 04Check CPU and battery information
- 05Inspect UI hierarchy and top activities
- 06Connect to devices and run shell commands
Use cases
- 01Operate Android app interfaces through an agent
- 02Check device display, CPU, and battery status
- 03Inspect the current activity and UI hierarchy
- 04Connect to a device and run shell commands
MCP support
The MCP server exposes Android input control, device information, UI and activity inspection, device connection, and shell execution as tools for MCP clients. It supports HTTP and stdio modes.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEアイリ Android
A MCP server that allows airi all LLMs to control Android devices. This project is a child project of airi.
Features
Input Control
input_tap- Tap on the screen at given coordinatesinput_swipe- Swipe from one coordinate to anotherinput_text- Input text on the deviceinput_keyevent- Send a key event to the deviceinput_press- Press the current keyinput_roll- Roll the trackball
Device Information
wm_size- Get the physical screen sizewm_density- Get the display densitycpu_percent- Get CPU usage percentagecpu_count- Get the number of CPU coresbattery_level- Get battery levelbattery_stats- Get detailed battery statistics
UI & Activity
ui_get_hierarchy- Get UI hierarchy (XML)utils_top_activity- Get the top activityutils_top_activities- Get all top activitiesutils_package_version- Get package version info
Device Management
device_connect- Connect to a device at specified host and portdevice_reset- Reset device connectionshell_execute- Execute any shell command
Usage
Docker (Recommended)
docker run --rm -it -p 3000:3000 -e ADB_HOST=host.docker.internal ghcr.io/proj-airi/airi-android:v0.3.4
# or stdio mode
docker run --rm -i -e USE_STDIO=true -e ADB_HOST=host.docker.internal ghcr.io/proj-airi/airi-android:v0.3.4
For agents supporting MCP, you can use the following configuration:
// mcp.json
{
"mcpServers": {
// http mode
"airi-android-http": {
"url": "http://localhost:3000/mcp"
},
// stdio mode
"airi-android-stdio": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"USE_STDIO=true",
"-e",
"ADB_HOST",
"ghcr.io/proj-airi/airi-android:v0.3.4"
],
"env": {
"ADB_HOST": "host.docker.internal"
}
}
}
}
Run Directly
Requires Bun to be installed.
# Install dependencies
bun install
# Start server (HTTP mode, port 3000)
bun run start
# Or use stdio mode
USE_STDIO=true bun run start
Development Setup
Prerequisites
- Install Bun
- Install Android Platform Tools
- Connect an Android device (via USB or
adb connectfor emulators)
Commands
# Install dependencies
bun install
# Run tests
bun test
# Start development server
bun run dev
# Build binary
bun run build
# Lint code
bun run lint
# Type check
bun run typecheck
Contributing
See AGENTS.md for code guidelines.
Environment Variables
| Variable | Description | Default |
|---|---|---|
USE_STDIO | Set to true to use stdio transport mode | false |
ADB_HOST | ADB server host address | localhost |
Tech Stack
- Bun - JavaScript runtime
- TypeScript - Type-safe JavaScript
- MCP SDK - Model Context Protocol SDK
- adbkit - ADB client library
- Hono - Web framework
- Zod - Schema validation
License
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.