mcp-android
Related Servers
Alternatives to mcp-android
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI agents to control Android devices via ADB, supporting gestures, input, screenshots, UI analysis, and app management.198 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to directly control Android devices via Termux, providing 120+ tools for screen manipulation, file management, app control, and system operations with layered loading and security gating.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control Android phones via MCP and HTTP. Supports screen capture, taps, swipes, text input, and app management.AGPL 3.0
- FlicenseBqualityBmaintenanceEnables 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.71-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to remotely control Android devices in the cloud via P2P WebRTC, providing tools for screenshots, touch input, file management, and automation scripts.17 npmMIT
- AlicenseAqualityFmaintenanceProvides AI agents with real-time vision and control over Android devices through screen streaming, UI automation, and fast input control via scrcpy protocol.3317MIT
TDQS
Scored across 65 tools
Many tools occupy overlapping territory: wait_idle, wait_change, wait_activity, ui_wait_for, and events_wait are all wait-like; status, device_info, capabilities, diagnostics, and the privilege status tools blur together; input_text and ui_set_text both set text; global_action and press_key both handle navigation. Descriptions help in some cases, but with 65 tools the boundaries are frequently unclear.
All tools share the android_ prefix and use clean snake_case, with strong domain grouping like android_file_*, android_ui_*, and android_notification_*. However, the verb/noun order is inconsistent (android_clipboard_get vs android_launch_app vs android_ui_find) and a few abstract nouns like android_flow and android_batch break the pattern.
65 tools is an extreme count for a single MCP server. Many could be consolidated, especially the status/privilege reports, wait variants, coordinate gesture tools, and execution helpers. The scope is broad, but the surface is not well-scoped.
The set covers UI observation and interaction, app launching and management, clipboard, notifications, media, volume, shell, logcat, file CRUD, and multi-step flows, so real workflows rarely dead-end. Minor gaps exist around app installation/uninstallation and direct system setting toggles, but most can be worked around via existing shell or intent tools.