androir-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_targetsA | List connected Android devices (serial, state, model) |
| statusA | Device info: state, properties, battery |
| screenshotB | Capture device screen as PNG |
| describe_screenA | Parse uiautomator UI tree; returns element labels and tap coordinates |
| tapB | Tap at screen coordinates (device pixels) |
| swipeB | Swipe from (x1,y1) to (x2,y2) |
| long_pressC | Long press at (x,y) |
| type_textA | Type text via adb input (spaces become %s) |
| press_keyC | Press a named key (home, back, enter, recents) |
| press_homeB | Press the home button |
| press_backC | Press the back button |
| launch_appC | Launch app by package name or friendly name |
| open_urlA | Open an http(s) URL in the default browser |
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 13 tools
Tools are mostly distinct, but press_key overlaps with press_back and press_home, causing potential confusion about which to use. Other tools like tap, long_press, and swipe are clearly differentiated.
Most tools follow a verb_noun pattern (e.g., describe_screen, launch_app, press_back). However, 'status' and 'screenshot' deviate as single nouns, and 'long_press' is slightly awkward. Overall, the convention is fairly consistent.
13 tools cover a broad range of Android interaction tasks without being overwhelming. Each tool serves a clear purpose, and the count is well-scoped for device automation.
The tool set covers core device operations: launching apps, UI tree parsing, input simulation, and device info. Minor gaps like scrolling or clipboard access are missing but can be worked around with existing tools.