"How to evaluate an app in an Android emulator" matching MCP servers:

An MCP server for managing local Android Virtual Devices (AVDs) and their lifecycles using Android SDK tools. It enables users to create, start, and stop emulators, while providing control over virtual sensors like the accelerometer and gyroscope.

Enables an AI agent to drive an Android app under development on a local emulator or connected device through adb, observing the screen and performing taps, swipes, text entry, key presses, waits, screenshots, logcat and crash inspection. It is restricted to debug builds installed via Run in Android Studio, so agents can exercise only the app being developed.

Enables Claude to control an Android phone over ADB by viewing screenshots and UI hierarchy and performing taps, typing, key presses, app launches, alarms/timers, and notification reads, with safe-by-default access modes and gated destructive actions.

Give any LLM agent a real Android or iPhone. 62 MCP tools: tap, swipe, type, screenshot, screen-tree reading, app launch, camera, TTS, crash reports, batched execution. Android via ADB, iPhone via WebDriverAgent, on-device inference, Docker+KVM emulators. Works with Claude Code, Cursor, LangChain, LlamaIndex, and any MCP client. MIT.

Enables MCP-compatible AI agents to perceive and control an Android phone through tools for screenshots, visible text and coordinates, app/screen queries, taps, swipes, text input, key events, app launching, and interrupt/resume, closing the perception-action loop.

Enables control of Android emulators (MumuEmulator or ADB-connected devices) through natural language, supporting app management, screen interactions (tap/swipe), screenshots, and device information retrieval.

A local, stdio-only Model Context Protocol server that lets coding agents inspect, control, and test Apple iOS Simulators and Google Android Emulators. It exposes 29 typed tools for device lifecycle, app management, UI automation, screenshots, logs, permissions, location, and platform-specific test conditions.

Lets AI agents use an Android phone: read the screen, tap, type, scroll, open apps, take screenshots and reply to notifications, with approval cards before anything is sent, posted, bought or deleted. Runs inside the Buddy app on the phone; no root, adb or PC.

An MCP server for automating virtual or physical Android devices using the Gbox SDK. It enables users to manage app installations, capture screenshots, and perform complex UI actions through natural language instructions.

Enables an AI client to control an Android emulator or USB device over ADB by selecting a device, inspecting the UI hierarchy, and performing taps, swipes, text entry, key presses, and app launches. It relies only on Android platform-tools and exposes a compatible tool surface for phone automation.

Enables AI agents to interact with Android devices through visual UI element detection and automated interactions. Provides comprehensive Android automation capabilities including touch gestures, text input, screenshots, and video recording via uiautomator2.

Enables Claude to see and control a real Android phone via MCP, reading the accessibility tree to tap, type, navigate, launch apps, and diagnose connectivity over ADB or cellular.

MCP server that lets an AI assistant see and control an Android phone over ADB: screenshots, UI dump, tap, swipe, type, keys, open apps. Safety guards: device allowlist, sensitive-app block, raw shell off by default, rate limit.

A lightweight bridge enabling AI agents to perform real-world tasks on Android devices such as app navigation, UI interaction, and automated QA testing without requiring computer-vision pipelines or preprogrammed scripts.

Provides powerful inspection and interaction tools for connected android devices or emulators.

Enables control and automation of Android devices using uiautomator2 and ADB. It supports UI interactions, app management, and shell command execution through the Model Context Protocol.

Enables Claude or any MCP agent to see and operate a real Android phone over adb, with fast screen reads, tap/type/swipe actions, app launching, deep links, and brand-aware setup guidance, all without admin rights or an Android SDK.

Enables interaction with Android devices and emulators through ADB, allowing control actions like tapping, text input, screenshots, UI inspection, and app launching through natural language.

Provides an MCP server that lets AI agents inspect and control an Android phone over Wi-Fi or USB, including screenshot element maps, OCR, taps, typing, scrolling, app launching, notifications, clipboard, and device settings/controls.

Enables MCP clients to turn Make blueprints and Zapier exports into n8n workflow files, with a per-step report of what converted, what to review, and what must be finished by hand. Also lists zaps, explains how individual steps are handled, checks workflow files for broken links or placeholders, and can upload the result to an n8n instance as an inactive workflow.