ADB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| adb_list_devicesA | List all connected Android devices |
| adb_get_device_infoC | Get detailed information about a specific device |
| adb_set_default_deviceC | Set the default device for subsequent operations |
| adb_screenshotC | Take a screenshot of the device screen |
| adb_clickC | Click at specific coordinates on the device screen |
| adb_swipeC | Swipe from one point to another on the device screen |
| adb_input_textC | Input text on the device |
| adb_press_keyC | Press a key on the device |
| adb_install_appC | Install an APK file on the device |
| adb_uninstall_appC | Uninstall an app from the device |
| adb_start_appC | Start an app on the device |
| adb_stop_appC | Stop an app on the device |
| adb_list_appsC | List installed apps on the device |
| adb_push_fileC | Push a file from local system to device |
| adb_pull_fileC | Pull a file from device to local system |
| adb_list_filesC | List files in a directory on the device |
| adb_shellC | Execute a shell command on the device |
| adb_get_system_infoC | Get system information from the device |
| adb_get_battery_infoC | Get battery information from the device |
| adb_get_logcatC | Get logcat output from the device |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Every tool has a clearly distinct purpose with no ambiguity - each targets a specific Android Debug Bridge operation like clicking, getting info, installing apps, or file management. The descriptions clearly differentiate actions like adb_click vs adb_swipe, adb_install_app vs adb_uninstall_app, and adb_pull_file vs adb_push_file.
All tools follow a perfect 'adb_verb_noun' pattern consistently throughout the entire set. The naming convention is uniform with clear action-object relationships, making it easy to understand what each tool does at a glance.
20 tools is slightly high but reasonable for comprehensive Android device management. The count covers essential ADB operations without obvious bloat, though some related operations like app clearing or system property setting could potentially be added or consolidated.
The toolset provides complete coverage for Android device management through ADB, including device listing/selection, app lifecycle management (install/start/stop/uninstall), file operations, input simulation, system information retrieval, and debugging capabilities. No significant gaps exist for core ADB workflows.