A
licenseNot graded
qualityC
maintenanceAn MCP server that lets AI agents control iOS and Android devices (tap, scroll, type, take screenshots, read UI trees, and run code). Works with multiple devices at the same time.
94 npm
54
MIT
erius-phone-mcp
by Protremix
Related Servers
Alternatives to erius-phone-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that gives AI agents full control of Android devices and emulators through plain ADB — no companion APK, no extra daemon, no telemetry.2614 npm12MIT
- AlicenseAqualityBmaintenanceAn MCP server that lets AI agents read Android and iOS screens as concise text and tap, type, and navigate real devices, pausing for human approval before sensitive actions like payments.1473AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceMCP server for Android Emulators to have easier experience with LLMs153MIT
- AlicenseAqualityCmaintenanceMCP server that gives AI agents full vision and control over Android devices via ADB and scrcpy. Supports screenshots, input, apps, UI automation, shell, files, and clipboard.38392 npm136MIT
- AlicenseBqualityDmaintenanceAn MCP server that allows AI agents to drive real Android devices via adb, capturing screenshots, reading the live UI tree, and performing actions like tap, swipe, and type.135 npm1Apache 2.0
TDQS
A3.5/5.0
Scored across 21 tools
Disambiguation4/5
Most tools map to clearly distinct device actions, and the descriptions proactively explain when to use alternatives (e.g. snapshot vs screenshot vs foreground, tap vs swipe vs scroll). Minor overlap exists: whoami and list_devices both surface device ids, and launch_app, open_url, and send_intent can all start an app/activity. Descriptions mostly resolve these, so an agent can usually pick the right one.
Naming Consistency4/5
All names are snake_case with a consistent convention and no style mixing. Most have a clear verb_noun form (get_device, launch_app, install_apk, wait_for_text), though several core interaction tools are bare nouns (snapshot, screenshot, foreground) or verbs (tap, swipe, scroll), which is a slight deviation.
Tool Count4/5
21 tools is on the heavier end but appropriate for a full device-automation/QA surface. Each tool corresponds to a real, distinct capability (input gestures, app lifecycle, inspection, crash logs). A few could theoretically be consolidated (whoami into list_devices) but nothing feels wasted.
Completeness4/5
Coverage is strong: device discovery, screen reading (snapshot/screenshot/foreground), all input gestures, app launch/install/uninstall, intents, URL opening, and crash logs are present. Minor gaps remain—no general logcat capture beyond crash buffer, and no file push/pull or clipboard for richer QA workflows.
Maintenance
ActivityMaintained
ResponsivenessOutdated data