
Android Puppeteer Mcp
io.github.pedro-rivasPublished by GitHub account pedro-rivasv1.0.1Updated Oct 24, 2026
MCP server for Android automation with UI interaction, screenshots, and device control
Overview
A local MCP server that lets an AI assistant inspect and control Android devices and emulators: annotated screenshots, taps, swipes, text input and screen video
- What you can do
- List connected Android devices and emulators and get their screen dimensions and interactive UI elements with details and numbered overlays on screenshots. Tap, long press, swipe, scroll and drag at coordinates, press the hardware back button, and type text into focused fields. Start and stop screen recording to local files for documentation or test runs. Target a specific device by ID when several are connected.
- When to use it
- Useful when an assistant should drive a real Android phone or emulator for UI testing, app walkthroughs, or scripted interactions, and when annotated screenshots or recorded video of the session are wanted.
- Requirements
- Runs locally as a Python package (Python 3.10+) with uiautomator2, ADB and an Android 10+ device or emulator with USB debugging enabled; scrcpy is needed for video recording. Host can be Windows, macOS or Linux. No API keys or environment variables are declared.
Installation
In SourceWeft
- Open Android Puppeteer Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-name: io.github.pedro-rivas/android-puppeteer-mcp
Android Puppeteer is a lightweight, visual-first MCP (Model Context Protocol) server that enables AI agents to interact with Android devices through intelligent UI element detection and automated interactions. Built on uiautomator2, it provides comprehensive Android automation capabilities including visual element detection, touch interactions, text input, and video recording.
Features
-
Visual Element Detection Automatically detects and annotates interactive UI elements with numbered overlays for precise targeting.
-
Comprehensive Touch Interactions Support for tap, long press, swipe, scroll, and drag gestures with coordinate-based precision.
-
Multi-Device Support Connect to multiple Android devices or emulators simultaneously with device-specific targeting.
-
Video Recording Integration Built-in screen recording capabilities using scrcpy for documentation and testing workflows.
-
Real-Time UI Analysis Live UI hierarchy parsing and element information extraction for dynamic interaction strategies.
-
MCP Protocol Integration Seamless integration with Claude Desktop and other MCP-compatible AI platforms.
Supported Operating Systems
- Android 10+
- Windows, macOS, Linux (host systems)
Installation
Prerequisites
- Python 3.10+
- uiautomator2
- Android 10+ (Emulator or Physical Device)
- ADB (Android Debug Bridge)
- scrcpy (for video recording features)
Getting Started
- Clone the repository
- Install dependencies
- Setup Android device
-
Connect to the MCP server
-
Locate your Claude Desktop configuration file:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:
-
Add the following JSON to your Claude Desktop config:
Replace:
path/to/uvwith the actual path to your uv executablepath/to/android-puppeteerwith the absolute path to where you have cloned this repo
-
Restart Claude Desktop
Restart your Claude Desktop. You should see "android-puppeteer" listed as an available integration.
Available Tools
Android Puppeteer provides the following tools for comprehensive Android device interaction:
Device Management
list_emulators: List all available Android emulators and devices with their status and dimensionsget_device_dimensions: Get the screen dimensions of a specific Android deviceget_ui_elements_info: Get detailed information about all interactive UI elements on screen
Visual Interaction
take_screenshot: Capture annotated screenshots with numbered UI element overlayspress: Tap on specific coordinates with optional long press durationlong_press: Perform long press gestures on specific coordinates
Navigation & Input
press_back: Press the hardware back buttonswipe: Perform directional or custom coordinate swipestype_text: Type text into focused input fields with optional text clearingscroll_element: Scroll specific UI elements in any direction
Recording & Documentation
record_video: Start screen recording with customizable quality settingsstop_video: Stop active screen recordings and save to local storage
Usage Examples
Basic Device Interaction
Multi-Device Automation
Video Recording Workflow
Project Structure
Important Notes
- Device Permissions: Ensure USB debugging is enabled on target Android devices
- Network Access: Some features require network connectivity for device communication
- Storage: Screenshot and video files are saved locally in
ss/andvideos/directories - Performance: Response times depend on device performance and network latency
Troubleshooting
Common Issues
- Device not found: Verify ADB connection with
adb devices - Permission denied: Check USB debugging and device authorization
- Screenshot failures: Ensure device screen is unlocked and accessible
- Video recording issues: Verify scrcpy installation and device compatibility
Debug Mode
Run the server directly for debugging:
License
This project is licensed under the MIT License. See LICENSE for details.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request. For major changes, please open an issue first to discuss what you would like to change.
Development Setup
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Make your changes
- Run tests and ensure code quality
- Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
Related Projects
- Android MCP - Alternative Android automation MCP server
- uiautomator2 - Core Android automation library
- MCP Protocol - Model Context Protocol specification
Star this repo if you find it useful!
Source: README.md at commit 94bf75f
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.