Android Screenshot MCP Server
Related Servers
Alternatives to Android Screenshot MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI agents to capture screenshots from Android devices and emulators, and manage connected devices for UI analysis and testing. Supports device listing, screenshot capture, and integrates with Claude Desktop, Gemini CLI, and GitHub Copilot.263 npm24MIT
- AlicenseBqualityDmaintenanceEnables control of Android devices via ADB, allowing screenshot capture, touch simulation, and swipe gestures through natural language commands.22190 npm6MIT
- FlicenseNot gradedqualityDmaintenanceEnables control of Android devices through ADB, allowing users to list connected devices, capture screenshots using multiple methods (adb, droidcast, minicap, mumu), and retrieve device information.-
- AlicenseAqualityBmaintenanceEnables debugging Flutter apps on Android by exposing the widget tree and source locations, supporting hot reload and pixel-level UI diffs, along with filtered Android logs, crash traces, and device interaction.26MIT
- AlicenseNot gradedqualityBmaintenanceEnables controlling an Android device from an MCP client via ADB, including wireless debugging discovery, UI-tree inspection, and performing taps, swipes, typing, app actions, and shell commands without relying on screen coordinates.1 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables remote control of Android devices via ADB, including screen operations, input, app management, file transfer, and advanced tools like UI testing and performance analysis.25MIT
TDQS
Scored across 2 tools
The two tools have overlapping purposes with unclear boundaries. Both are focused on taking Android screenshots, with 'connect_and_screenshot' implying connection and capture, while 'screenshot' can also handle connections if needed. This creates ambiguity about when to use each tool, as their descriptions suggest similar functionality with minor variations in connection handling.
The tool names follow a consistent snake_case pattern and use clear verbs ('connect_and_screenshot', 'screenshot'). While the naming is technically consistent, the inclusion of 'connect_and_' in one name versus not in the other creates a minor deviation in structure, but overall the naming is readable and follows a predictable style.
With only 2 tools, the server feels thin for its purpose of Android screenshot management. While it covers basic screenshot functionality, the limited tool count may restrict more advanced operations or device management tasks, placing it in the borderline range where the scope seems underdeveloped.
The tool set is significantly incomplete for Android device interaction. It only provides screenshot capabilities without covering essential operations like listing devices, managing connections, handling multiple devices, or performing other common ADB commands. This creates gaps that could lead to agent failures when broader device control is needed.