Android 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_logcat_outputB | 从已连接的 Android 设备获取最近 100 行日志。 |
| get_screenshotA | 获取已连接 Android 设备的屏幕截图。 用于检查界面视觉效果；若需识别元素，优先使用 get_ui_dump。 |
| get_ui_dumpA | 获取 XML 格式的 UI 视图层级，用于理解屏幕结构和定位元素。 |
| tap_screenA | 在屏幕指定坐标执行点击操作。坐标应从 get_ui_dump 的 bounds 属性动态获取。 |
| swipe_screenC | 在屏幕上执行滑动操作，从起点滑动到终点。 |
| send_textA | 模拟键盘向当前焦点输入框发送文本。注意：不支持中文，中文请使用其他输入法方案。 |
| perform_system_actionB | 执行系统级操作，如返回、回到主页或打开最近任务列表。 |
| get_device_infoA | 获取已连接 Android 设备的基本信息，包括型号、系统版本、分辨率、序列号等。返回 JSON 格式字符串。 |
| get_current_activityA | 获取当前前台运行的 Activity 名称，用于定位当前所在页面。 |
| launch_appB | 启动指定包名的 Android 应用（使用 monkey 命令）。 |
| force_stop_appB | 强制停止指定包名的 Android 应用。 |
| clear_app_dataA | 清除指定应用的所有数据和缓存（相当于「清除数据」操作）。 |
| install_apkB | 将本地 APK 文件安装到已连接的 Android 设备。 |
| get_app_listB | 列出设备上已安装的应用包名列表。 |
| get_memory_infoB | 获取指定应用的内存占用信息（PSS、RSS 等）。 |
| pull_fileC | 从 Android 设备拉取文件到本地。 |
| push_fileC | 将本地文件推送到 Android 设备。 |
| long_pressB | 在屏幕指定坐标执行长按操作（通过零距离滑动模拟）。 |
| grant_permissionC | 为指定应用授予运行时权限。 |
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 19 tools
Each tool targets a distinct device operation with clear boundaries: gestures (tap/long_press/swipe), file transfer (push/pull), app lifecycle (launch/force_stop/clear_data/install), and info gathering (device/memory/logcat/activity) do not overlap. The descriptions even disambiguate similar tools like get_ui_dump vs get_screenshot, directing agents to the right one.
All names are snake_case and verb-first, following a predictable verb_noun pattern (get_device_info, push_file, launch_app, clear_app_data). Minor variation like long_press/tap_screen still fits the scheme cleanly.
19 tools is slightly above the ideal 3-15 band but each earns its place in a device-automation surface. The set is cohesive rather than padded, so it's a minor overage rather than a scope mismatch.
Strong coverage of input, app lifecycle, file transfer, permissions, and introspection for Android automation. Minor gaps exist (no uninstall/revoke_permission, no element-text convenience, no waiting/rotation), but core workflows are fully supported.