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.213 npm25MIT
- AlicenseBqualityDmaintenanceEnables control of Android devices via ADB, allowing screenshot capture, touch simulation, and swipe gestures through natural language commands.22103 npm6MIT
- AlicenseNot gradedqualityAmaintenanceLets AI agents see and use a real Android phone over Wi-Fi: read the screen, find elements by text or ID, tap, type, swipe, take screenshots and read notifications, without ADB or root.312MIT
- 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.-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to see and control Android devices by capturing screenshots as images, tapping, swiping, typing, launching apps, inspecting UI elements, transferring files, streaming audio/video, and running shell commands. Uses scrcpy's binary control protocol for fast input and near-instant screenshots, with ADB fallback for interaction tools.151 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables a local coding agent to control and inspect an Android phone over the user's own Wi-Fi, with on-device consent and an app blocklist. Provides tools to read the screen, take screenshots, tap, swipe, type, scroll, and navigate Back, Home, or Recents.MIT
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.