A
licenseB
qualityB
maintenanceEnables AI assistants to interact with Android devices and emulators via ADB, providing tools for screenshots, UI inspection, touch and text input, app management, and device control.
42
46 npm
17
MIT
autoglm-mcp-server
by DarkNoah
Related Servers
Alternatives to autoglm-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables control of Android devices via ADB, allowing screenshot capture, touch simulation, and swipe gestures through natural language commands.22130 npm6MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to control and manage Android devices via ADB, including app installation, UI interaction, and device monitoring.12GPL 3.0
- AlicenseBqualityCmaintenanceEnables AI agents to control Android devices via ADB, supporting gestures, input, screenshots, UI analysis, and app management.198 npmISC
- FlicenseBqualityCmaintenanceEnables AI assistants to observe, reason about, and control connected Android devices via ADB, providing tools for screenshots, UI hierarchy parsing, semantic element clicking, gestures, text input, and app lifecycle management.13-
- AlicenseBqualityBmaintenanceEnables AI agents to control Android TV/Android devices through ADB, including screen capture, remote control, app management, and more.241 npmMIT
TDQS
A3.8/5.0
Scored across 3 tools
Disambiguation4/5
The three listed tools are clearly separated: connecting to a device, listing connected devices, and running an autonomous task. However, autoglm_task references autoglm_execute_action, a tool that is not actually exposed by this server, which could lead an agent to expect or attempt a nonexistent tool.
Naming Consistency2/5
Tool names mix conventions: adb_connect lacks the autoglm_ prefix used by the other two tools, and autoglm_task is a noun rather than a verb-based action name like autoglm_list_adb_devices or adb_connect. The mention of autoglm_execute_action adds another inconsistent naming style not present in the actual tool set.
Tool Count4/5
Three tools is minimal but each covers a necessary stage of the ADB/AutoGLM workflow: connect, list devices, and execute a task. The count feels slightly thin because autoglm_task implies a separate single-action execution tool should exist.
Completeness2/5
The server covers device connection, device listing, and autonomous task execution, but autoglm_task explicitly tells users to use autoglm_execute_action for single known actions, and that tool is missing. This is a significant gap because the intended workflow cannot handle simple direct actions without falling back on the missing tool.
Maintenance
ActivityInactive
ResponsivenessNo issues