"A server for debugging and testing Android apps with A11y compliance" matching MCP servers:

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

Android MCP — 76 ADB-based tools for device, apps, UI, logcat, emulator, files, system, and debug. Includes 7 workflow Prompts (crash investigation, ANR, battery drain).

Secure, read-only MCP server that lets AI assistants (Claude, OpenCode, VS Code) inspect Android devices via ADB — logcat, UI hierarchy, installed packages, and allowlisted shell commands. TypeScript/Node.js.

fork from https://github.com/JoshuaRileyDev/mac-apps-launcher

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 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.

Enables Android device control via ADB and scrcpy, including device management, app management, file operations, shell commands, input simulation, screen mirroring, and UI element inspection.

Enables full Android control from any AI agent via 7 MCP tools, including screen capture, touch interaction, app management, and system control.

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.

Enables control of Android devices via ADB for automation and testing. Supports app management, screen capture, UI analysis, and input simulation through natural language commands.

Enables LLMs to control and manage Android devices via ADB, including app installation, UI interaction, and device monitoring.

Enables comprehensive Android device control over ADB, including UI automation, screen capture/recording, app management, file operations, and log/notification access, with a built-in permission system.

A local MCP bridge that lets ChatGPT chat mode operate the user's own computer, running project, file, and shell tasks through a local executor and returning progress and results to the conversation. It also coordinates Codex sessions (persistent or one-off) and other agent CLIs as sub-agents.

An MCP server that wraps Android ADB functionality into AI assistant tools, enabling device management, shell execution, file operations, app management, media capture, and log analysis via natural language.

Enables ChatGPT web to read local files, search code, run shell commands, and drive a local Codex CLI via an official MCP connector, with human approval for risky commands and full audit logging.

Unofficial Powershell MCP server

A minimal MCP server that exposes a run_command tool over stdio, enabling command execution within a Docker container.

Enables an AI agent to operate a spare Android phone through MCP: capture screenshots, inspect UI controls, tap/swipe, input Chinese text, launch apps, and optionally run rooted shell commands or transfer files. It also supports a live web console for remote viewing and control.

MCP server that gives AI agents isolated, named Linux computers with stable IDs and lifecycle control. Supports multiple backends like Docker, Fly Machines, Modal, and E2B, with a dashboard for managing sandboxes.

Enables forensic investigators to acquire data from Android devices via ADB, including device backup, artifact collection, and secure command execution.