DeepADB
Related Servers
Alternatives to DeepADB
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceA comprehensive MCP server for Android Debug Bridge, enabling AI agents to control Android devices through structured tools like launching apps, UI automation, file operations, and log capture.907MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps Android ADB functionality into AI assistant tools, enabling device management, shell execution, file operations, app management, media capture, and log analysis via natural language.23 npm3MIT
- FlicenseNot gradedqualityDmaintenanceA powerful MCP server that provides comprehensive Android device automation capabilities through ADB, enabling AI agents to interact with Android devices for testing, automation, and device control tasks.1-
- AlicenseBqualityAmaintenanceA local MCP server that controls Android devices via ADB, enabling AI agents and users to manage devices, execute UI automation, and perform testing through 27 MCP tools and an optional web console.271MIT
- AlicenseAqualityCmaintenanceA MCP server that enables AI assistants to control Android devices via ADB, supporting device info, screen control, input simulation, app management, shell execution, file transfer, and UI parsing.20MIT
- FlicenseAqualityDmaintenanceAn MCP server designed for Android development, enabling AI assistants to directly control Android devices for screenshots, UI analysis, app management, and more.19-
TDQS
Scored across 209 tools
Many tools overlap in purpose: adb_screencap, adb_screencap_annotated, adb_screenshot_compressed, adb_screenshot_baseline, adb_screen_state, adb_device_state, and adb_current_activity all partially overlap on screenshots/state. Likewise adb_input vs. adb_input_tap/swipe/text/drag/fling/long_press/double_tap/pinch/batch_actions, and adb_health_check vs. adb_runtime_audit vs. adb_ci_device_ready create real selection ambiguity. Descriptions help, but an agent can easily pick a plausible-but-suboptimal tool.
Nearly all tools use the adb_ prefix with snake_case and mostly action-oriented names, which is predictable. Minor deviations exist in ordering and abstraction level (adb_file_chmod vs. adb_chmod-style naming, adb_screen vs. adb_screencap, and mixed resource/action ordering), but the convention is still readable.
209 tools is far beyond what is appropriate even for a broad ADB automation platform, and many tools are narrow wrappers or convenience combinations. The surface is large enough to overwhelm tool selection and materially increases the chance of misselection.
Coverage is unusually broad: device management, file operations, UI automation, input, networking, telephony/radio, firmware, QEMU, testing, workflows, and plugins are all represented. There are minor lifecycle gaps such as deletion/cleanup for saved profiles, baselines, or workflows, but core workflows are well covered.