android-mcp-toolkit
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert-svg-to-android-drawableA | Convert SVG markup or files into Android VectorDrawable XML quickly, optionally writing to disk. |
| manage-logcatA | Unified tool to read logs, capture crashes, check ANRs, and clear buffers. |
| get-current-activityB | Inspect current focused app/window via dumpsys window. |
| estimate-text-length-differenceA | Compare original and translated text lengths to detect layout risk; configurable tolerancePercent (default 30%). |
| dump-ui-hierarchyB | Capture the current UI hierarchy as XML using uiautomator. |
| take-screenshotB | Capture device screenshot and save to a local file. |
| inject-inputB | Simulate user input interactions (tap, text, swipe, keyevents) or click by UI element. |
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 7 tools
Each tool targets a distinct aspect of Android device interaction: drawing conversion, UI hierarchy, text estimation, activity info, input simulation, logcat management, and screenshot capture. No two tools overlap in purpose.
Most tools follow a verb-noun pattern (e.g., dump-ui-hierarchy, inject-input), but 'convert-svg-to-android-drawable' breaks this pattern with a longer descriptive phrase. Overall, the naming is still readable and predictable.
Seven tools cover the essential aspects of Android device testing and automation without being overwhelming. The count is well-scoped for the toolkit's purpose.
The toolkit covers core UI testing operations (hierarchy, input, screenshot, logcat) but lacks tools for app management, clipboard access, or device configuration. The inclusion of SVG conversion and text length estimation adds niche functionality, but common tasks like UI element querying (beyond typing coordinates) are missing.