An MCP server for android automation
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-android-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Android MCP Server An MCP (Model Context Protocol) server that provides programmatic control over Android devices through ADB (Android Debug Bridge). This server exposes various Android device management capabilities that can be accessed by MCP clients like [Claude desktop](https://modelcontextprotocol.io/quickstart/user) and Code editors (e.g. [Cursor](https://docs.cursor.com/context/model-context-protocol)) ## Features - 🔧 ADB Command Execution - 📸 Device Screenshot Capture - 🎯 UI Layout Analysis - 📱 Device Package Management ## Prerequisites - Python 3.x - ADB (Android Debug Bridge) installed and configured - Android device or emulator (not tested) ## Installation 1. Clone the repository: ```bash git clone https://github.com/minhalvp/android-mcp-server.git cd android-mcp-server ``` 2. Install dependencies: This project uses [uv](https://github.com/astral-sh/uv) for project management via various methods of [installation](https://docs.astral.sh/uv/getting-started/installation/). ```bash uv python install 3.11 uv sync ``` ## Configuration The server supports flexible device configuration with multiple usage scenarios. ### Device Selection Modes **1. Automatic Selection (Recommended for single device)** - No configuration file needed - Automatically connects to the only connected device - Perfect for development with a single test device **2. Manual Device Selection** - Use when you have multiple devices connected - Specify exact device in configuration file ### Configuration File (Optional) The configuration file (`config.yaml`) is **optional**. If not present, the server will automatically select the device if only one is connected. #### For Automatic Selection Simply ensure only one device is connected and run the server - no configuration needed! #### For Manual Selection 1. Create a configuration file: ```bash cp config.yaml.example config.yaml ``` 2. Edit `config.yaml` and specify your device: ```yaml device: name: "your-devi…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.