MCP Scrcpy Vision
Related Servers
Alternatives to MCP Scrcpy Vision
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceGives AI agents vision and control over Android devices through ADB and scrcpy, letting them capture and actually see the screen, tap, swipe, type, launch and manage apps, find UI elements, stream video and audio, transfer files, and run shell commands. Interaction uses scrcpy's fast binary control protocol for near-instant screenshots and 10-50x faster input, with an ADB fallback when no session is active.374 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to see and control Android devices through ADB and scrcpy, offering fast screenshots, input, UI automation, app management, file transfer, shell commands, and audio/video streaming.374 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to see and control Android devices over ADB and scrcpy—taking screenshots, tapping, swiping, typing, launching apps, inspecting UI elements, transferring files, streaming video/audio, and running shell commands. It uses scrcpy's control protocol for fast input and near-instant screenshots, with ADB fallback when scrcpy is unavailable.374 npmMIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents vision and control over Android devices through ADB and scrcpy, enabling screenshots, taps, swipes, typing, app launching, UI inspection, file transfer, and shell commands. Uses scrcpy's control protocol for fast input and near-instant screenshots, with ADB as a fallback.374 npmMIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents vision and control over Android devices via ADB and scrcpy, enabling screen capture, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, audio/video streaming, and clipboard access.374 npmMIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents vision and control over Android devices through ADB and scrcpy, enabling them to capture screenshots, tap, swipe, type, launch and manage apps, inspect UI elements, stream audio and video, transfer files, and run shell commands. Input and screenshots run over a fast binary control protocol when a session is active, with ADB fallback so interaction keeps working without scrcpy.374 npmMIT
TDQS
Scored across 33 tools
Most tools have distinct purposes, but some overlap exists, such as android.input.swipe and android.input.dragDrop, which both involve screen gestures and could cause confusion. However, descriptions clarify their specific uses, and other tools are well-separated by domain (e.g., adb, input, screen, vision).
Tool names follow a highly consistent pattern of domain.subdomain.action (e.g., android.adb.connectWifi, android.input.tap, android.screen.wake). This hierarchical naming scheme is predictable and aids in understanding the tool's purpose and category.
With 33 tools, the count is excessive for a server focused on Android device control and vision. Many tools could be consolidated or omitted without losing functionality, leading to a bloated interface that may overwhelm agents and increase selection errors.
The tool set comprehensively covers Android device interaction, including adb connectivity, app management, file operations, input simulation, screen control, UI inspection, and vision streaming. There are no obvious gaps; it supports full lifecycle operations from setup to advanced automation.