airtest-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRTEST_IDE_ROOT | No | Directory containing AirtestIDE.exe. Required unless auto-detected. | |
| AIRTEST_MCP_RUNS_DIR | No | Directory for generated temporary .air projects. |
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 |
|---|---|
| airtest_infoA | Return the detected AirtestIDE, runner and bundled ADB paths. |
| list_android_devicesA | List Android devices visible to the ADB bundled with AirtestIDE. |
| run_airtest_scriptB | Run an existing .air directory with an optional Airtest device URI. |
| run_airtest_codeB | Run trusted, hand-written Airtest Python code in a temporary .air project. |
| snapshotB | Capture a device screenshot to an absolute local path. |
| touchC | Touch an absolute screen coordinate. |
| swipeC | Swipe between two absolute screen coordinates. |
| keyeventC | Send an Airtest key event, primarily for Android. |
| start_appC | Start an Android package or iOS bundle identifier. |
| stop_appB | Stop an Android package or iOS bundle identifier. |
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 10 tools
Most tools have clearly distinct purposes. The only potential ambiguity is between run_airtest_script and run_airtest_code, but their descriptions clarify that one runs a .air directory while the other executes inline code. No other tools overlap significantly.
All tool names use snake_case, but the pattern is mixed: some are verb_noun (list_android_devices, start_app), while others are single verbs (touch, swipe) or nouns (airtest_info, snapshot, keyevent). This inconsistency is minor, as the names are short and readable.
With 10 tools, the server is well-scoped for mobile automation. Each tool covers a core operation, and the count is appropriate for the domain without feeling sparse or overwhelming.
Core workflows are covered: device discovery, script/code execution, screenshot capture, UI interactions, and app lifecycle. Missing features like text input or screen size query can be worked around via run_airtest_code, so gaps are minor.