# docker-android [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/budtmo/docker-android  
**GitHub Stars:** 16067  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/docker-android

## Description
Android in docker solution with noVNC supported, video recording, mcp server and AI-agent

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What docker-android does

docker-android packages Android emulators in Docker containers and adds an HTTP MCP server for agent-driven workflows. The images are intended for native, web, and hybrid Android application development, as well as unit and UI testing with frameworks such as Appium and Espresso.

The available emulator images cover Android 9 through Android 14, with API levels 28, 29, 30, 32, 33, and 34. Device profiles include phones such as the Samsung Galaxy S6 through S10, Nexus models, and tablets including the Nexus 7 and Pixel C. A separate Genymotion image is also available.

## How it works

Run an Android image as a Docker container and expose the MCP endpoint over HTTP. The container can also provide browser-based VNC access on port 6080, allowing a developer or agent to observe the emulator through a web browser. Android emulator access from outside the container is available through ADB connect.

The project provides an MCP-specific image tag in addition to the Android-version image tags. Its MCP server and AI-agent support are marked as beta. Local-LLM support for the AI-agent feature includes Ollama and VLLM.

Emulator state is removed when the container restarts by default. Mounting a volume at `/home/androidusr` preserves the emulated device data between restarts.

## Setup and configuration

Docker is required, and the host must support hardware virtualization. The documented quick start targets Ubuntu; macOS and Windows hosts require a virtual machine running Ubuntu because the image runs under Ubuntu only. The example also passes `/dev/kvm` into the container for emulator acceleration.

A basic container launch uses an emulator device name and enables web VNC:

```bash
docker run -d \
  -p 6080:6080 \
  -e EMULATOR_DEVICE="Samsung Galaxy S10" \
  -e WEB_VNC=true \
  --device /dev/kvm \
  --name android-container \
  budtmo/docker-android:emulator_11.0
```

Open `http://localhost:6080` to view the running emulator. Check its status with:

```bash
docker exec -it android-container cat device_status
```

For persistent data, mount a Docker volume at `/home/androidusr`. Windows 11 users running through WSL2 need nested virtualization and appropriate `/dev/kvm` permissions; the setup includes changes to `.wslconfig`, `/etc/wsl.conf`, and a WSL restart.

## Tools and capabilities

- HTTP MCP support for AI-agent interaction with the Android container
- Android emulator profiles for phones and tablets
- Browser-based VNC viewing through port 6080
- Video recording support
- Web-accessible log sharing
- External emulator control through ADB connect
- Android project builds and automated unit or UI testing
- Appium MCP support
- Integration with Genymotion cloud services

## Limitations and notes

The MCP server is presented as a beta feature. The normal Docker-Android image requires an Ubuntu environment and hardware virtualization, including access to `/dev/kvm`. Container restarts discard emulator data unless `/home/androidusr` is backed by a volume.

The documented AI-agent support is also beta and lists Ollama and VLLM as supported local-LLM servers. The project distinguishes the normal and sponsor-based Pro versions; features such as the AI agent, newer Android versions, proxy configuration, headless mode, and Selenium 4.x integration are listed under Pro rather than the normal version.

_Full upstream README: https://allmcps.com/mcp/docker-android/readme_