app-screen-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_simulatorsB | List all available iOS simulators with their state (Booted, Shutdown, etc.) |
| boot_simulatorC | Boot an iOS simulator by UDID |
| terminate_appA | Terminate (force-quit) an app on a simulator |
| launch_appC | Launch an app on a simulator |
| get_ui_treeC | Get the full accessibility/UI tree as structured JSON. |
| take_screenshotB | Take a JPEG screenshot with optional compression and unchanged-image suppression. |
| get_screen_summaryC | Get screen context (UI tree and optional screenshot) with token-saving options. |
| tapB | Tap at specific (x, y) coordinates on the simulator screen |
| tap_relativeA | Tap using relative coordinates (rx, ry) in [0,1] where (0.5, 0.5) is center. |
| type_textC | Type text into the currently focused element on the simulator |
| swipeC | Perform a swipe gesture from one coordinate to another |
| press_buttonB | Press a hardware button on the simulator |
| find_elementsC | Search the UI tree for elements whose label, value, or hint contains query text |
| tap_textA | Find a UI element by visible text and tap its center. |
| tap_idA | Find a UI element by its accessibility identifier and tap its center. |
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 15 tools
Most tools have distinct purposes with clear boundaries, such as boot_simulator vs. launch_app, or tap vs. swipe. However, some overlap exists between tap, tap_id, tap_relative, and tap_text, which all perform tapping actions but with different targeting methods, which could cause minor confusion in selection.
Tool names consistently follow a verb_noun or verb pattern with snake_case throughout, such as boot_simulator, find_elements, and take_screenshot. This uniformity makes the set predictable and easy to understand at a glance.
With 15 tools, the count is well-scoped for an iOS simulator automation server, covering essential operations like simulator management, UI interaction, and app control without being excessive. Each tool serves a clear purpose, justifying its inclusion.
The toolset provides comprehensive coverage for iOS simulator automation, including simulator booting, app launching/termination, UI navigation, and input actions. A minor gap is the lack of tools for more complex gestures or app state queries, but core workflows are well-supported.