F
licenseA
qualityB
maintenanceMCP server for controlling Android, Fire TV, and Android TV devices through ADB, enabling device management, app operations, screenshots, UI dumps, and OBS recording.
30
-
@wilsonbeam/openclaw-adb-mcp
by wilsonbeam
Related Servers
Alternatives to @wilsonbeam/openclaw-adb-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceMCP server for Android emulator automation via ADB.17514MIT
- 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-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that controls real Android devices via ADB, offering screen vision, input automation, and device management tools.1MIT
- FlicenseAqualityDmaintenanceA 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.20-
- FlicenseNot gradedqualityCmaintenanceA lightweight MCP server for Android operating system automation. This server provides tools to interact directly with Android devices and app interaction with control3-
TDQS
B3.4/5.0
Scored across 30 tools
Disambiguation5/5
Every tool has a clearly distinct purpose with detailed descriptions. Even related actions like make_call vs dial_number are unambiguously differentiated by their behavior, and press_key vs press_home/back are specific. No two tools appear to perform the same function.
Naming Consistency4/5
The naming pattern is mostly consistent with the 'adb_' prefix followed by a verb and object (e.g., install_app, push_file, answer_call). However, a few names are noun phrases or queries (device_info, screen_size, call_state, is_locked), deviating from the verb-first style and creating minor inconsistency.
Tool Count2/5
With 30 tools, this server exceeds the typical well-scoped range and crosses the 25+ threshold. While each tool has a distinct purpose, the large number can overwhelm agents and many could be consolidated via parameters, making the count feel excessive for most use cases.
Completeness4/5
The tool set covers a wide range of ADB operations including device management, app lifecycle, file transfer, UI automation, telephony, and locking. Notable omissions like reboot and logcat are not directly exposed, but the adb_shell tool allows these to be executed manually, so agents can work around these gaps effectively.
Maintenance
ActivityInactive
ResponsivenessNo issues