A
licenseB
qualityD
maintenanceMCP server for Android device automation via ADB, enabling screen control, phone functions, app management, and device control.
30
1
MIT
polyscreen-mcp
by Shenepoy
Related Servers
Alternatives to polyscreen-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for controlling Android devices over ADB, using direct commands and semantic accessibility selectors with a Kotlin helper APK.71 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that controls real Android devices via ADB, offering screen vision, input automation, and device management tools.4MIT
- 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-
- AlicenseBqualityBmaintenanceMCP server for Android emulator automation via ADB.1717 npm4MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that provides tools for controlling Android devices using uiautomator2, enabling AI to automate tasks like tapping, swiping, and managing apps.168 PyPI53Apache 2.0
TDQS
B3.4/5.0
Scored across 43 tools
Disambiguation4/5
Most tools have distinct resource/action targets, and descriptions explicitly distinguish blocking vs async recording/focus and input variants. Some overlap remains among UI node reads (snapshot/find/wait) and capture/record families, but guidance usually clarifies selection.
Naming Consistency4/5
All tools use a mobile_ prefix and snake_case, so the convention is broadly readable. However the ordering is mixed: many use noun_verb (mobile_screen_capture, mobile_app_launch) while others use verb_noun (mobile_open_url, mobile_analyze_recording).
Tool Count2/5
43 tools is heavy for one device-automation server; many variants (blocking vs async capture/record/focus, several input primitives) could be consolidated or grouped. The broad Android testing scope justifies some breadth, but the surface exceeds the 25-tool threshold in the rubric.
Completeness4/5
Coverage is broad across device/display discovery, capture, recording, UI inspection, input, app lifecycle, location, clipboard, and batching. Minor gaps include no direct logcat tool despite session status mentioning logcat, and no generic file/shell operations, but core device-control workflows are well supported.
Maintenance
ActivityMaintained
ResponsivenessNo issues