"Android Studio Development Platform" matching MCP servers:

Enables an agent to drive an Android phone attached via USB by reading the screen, deciding next steps, executing actions, and verifying results, all through adb.

An MCP server that gives AI agents full control of Android devices and emulators through plain ADB — no companion APK, no extra daemon, no telemetry.

Enables AI agents to control, inspect, and automate Android devices, Waydroid containers, and AVD emulators over ADB. Provides tools for screenshots, UI-hierarchy text-based tapping, gestures, key presses, text input, app management, and raw shell commands.

Enables AI agents to control Android devices and emulators through direct UI interaction, allowing app navigation, automated testing, and real-world task execution via ADB without computer vision or scripts.

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 AI agents to control Android devices via ADB, supporting gestures, input, screenshots, UI analysis, and app management.

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.

A local MCP server that controls Android devices via ADB, enabling AI agents and users to manage devices, execute UI automation, and perform testing through 27 MCP tools and an optional web console.

MCP server for Android emulator automation via ADB.

Enables an AI agent to control an Android phone over a private Tailscale network via accessibility UI automation, screenshots, gestures, notifications, clipboard, intents, SAF file access, and optional Termux/Shizuku shells without root or ADB.

A MCP server that enables LLMs to control Android devices via ADB, supporting input, UI hierarchy, device management, and shell commands.

MCP server for Android device management via ADB, enabling inspection and configuration of Android devices over USB or Wi-Fi.

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 full Android control from any AI agent via 7 MCP tools, including screen capture, touch interaction, app management, and system control.

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.

AI-powered Android device automation via MCP. Control an Android phone with natural language through Claude Desktop, Cherry Studio, Kai 9000, or the built-in Web GUI.

MCP server that enables LLMs to control Android devices via ADB, providing tools for screen interaction and UI inspection.

Enables an agent to inspect and interact with Android emulators or physical devices via ADB, capturing UI snapshots, tapping nodes, typing text, and reading app logs.

MCP server for controlling Android devices via semantic actions with verification, enabling any MCP client to interact with phones through natural language and structured tools.