No user-submitted related servers found.
Scored across 35 tools
Most tools target a clearly distinct resource+action, and the local vs. remote device listing pair is explicitly disambiguated in the descriptions. The main soft spot is mobile_take_screenshot vs mobile_save_screenshot, which are easy to misselect, and mobile_batch_commands is an umbrella that overlaps with every other tool by design.
The dominant mobile_verb_noun pattern is strong, but there are several deviations: get_more_tools lacks the mobile_ prefix, mobile_clipboard has no verb despite doing read and write, and gesture tools are named inconsistently (mobile_double_tap_on_screen vs. mobile_click_on_screen_at_coordinates / mobile_long_press_on_screen_at_coordinates, the latter names no longer matching their element-ref capability). Readable overall, but the convention is not uniform.
35 tools is heavy for a mobile automation server, though the surface spans several genuinely distinct areas (local devices, cloud fleet, app lifecycle, UI interaction, media capture, diagnostics), so most tools earn their place. Still, some adjacent pairs (take/save screenshot, clipboard read/write, batch wrapper) inflate the count beyond what the core workflows require.
Coverage is broad: device discovery and provisioning, full app lifecycle (install/uninstall/launch/terminate/clear data), tap/double-tap/long-press/swipe/type interaction, element listing with refs, screenshots, recording, orientation, fold, location, clipboard, logs, and crashes. Gaps are minor — no explicit scroll or pinch/multi-touch gesture, no device info/battery/network state, and no file push/pull.