visor-mcp
Related Servers
Alternatives to visor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables interaction with Android devices via the Android Debug Bridge (ADB), allowing users to manage apps, files, and system permissions through natural language commands. It supports core functions like package listing, screen captures, and APK installation within MCP-compatible environments like Claude and Windsurf.130 npm15MIT
- AlicenseNot gradedqualityDmaintenanceEnables programmatic control of Android devices via ADB, supporting UI automation, app management, screen capture with OCR, and file transfers through the Model Context Protocol. It allows MCP-compatible clients like Claude Desktop and Cursor to interact directly with physical or emulated Android devices.3Apache 2.0
- AlicenseBqualityBmaintenanceEnables AI agents to control Android TV/Android devices through ADB, including screen capture, remote control, app management, and more.241 npmMIT
- AlicenseBqualityBmaintenanceEnables AI assistants to interact with Android devices and emulators via ADB, providing tools for screenshots, UI inspection, touch and text input, app management, and device control.4246 npm17MIT
- FlicenseNot gradedqualityDmaintenanceExposes Android device control via adb and scrcpy as 22 tools for MCP clients like Claude Code and Codex CLI.2-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control Android devices via ADB, providing tools for screen capture, tap/swipe/input, app management, and diagnostics. Works locally over USB or WiFi and integrates with MCP clients like Claude and Cursor.1MIT
TDQS
Scored across 29 tools
Most tools have distinct purposes, but closely related pairs like quest_logs/quest_logs_stream and quest_performance/quest_monitor may require careful reading of descriptions to select correctly. The detailed tool descriptions largely resolve ambiguity.
All tools use the quest_ prefix and snake_case, but the naming pattern is mixed: some are verb-first (quest_install, quest_launch), some are noun-first (quest_app_list, quest_frame_timing), and others are single nouns (quest_thermal, quest_info). This inconsistency is readable but not uniform.
With 29 tools, the server exceeds the typical well-scoped range (3-15) and falls into the 'too many' category. While the broad domain justifies many tools, the heavy count can overwhelm an agent and includes several closely related performance/logging utilities.
The toolset provides comprehensive coverage of Quest device management and debugging: app lifecycle, file transfer, logging, crash reporting, performance profiling, screen capture, and device status. No major gaps or dead ends are apparent for the stated purpose.