twiddle-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 |
|---|---|
| wait_forA | BLOCK until text or an element appears (or disappears with state:'gone') — use this instead of screenshot+sleep loops. Returns immediately when the condition is met, with elapsed time and a semantic diff of what changed. On timeout it returns matched:false plus the current UI tree (never throws) so you can see what IS on screen. |
| wait_for_idleA | BLOCK until the UI stops changing (animations/loads settled). Volatile elements like clocks and spinners marked noisy are ignored. Use after navigation before reading the screen. |
| get_ui_treeA | Get the current accessibility tree as structured text with [ref=eN] markers usable in tap/type_text. Much cheaper and more precise than a screenshot. |
| ui_diffA | Semantic diff of the current UI vs a previous snapshot (default: the last one this server took). Answers 'what changed?' without comparing screenshots. |
| list_devicesA | List iOS simulators and Android emulators/devices. Booted devices first; use the returned id with every other tool. |
| launch_appB | Launch an app by iOS bundle id or Android package name. |
| terminate_appC | Terminate a running app. |
| tapA | Tap an element by [ref=eN] from get_ui_tree/wait_for, by selector, or by x/y. Refs re-resolve against the live tree; if the element is gone you get the current tree instead of a blind tap. With scroll:true, a selector that isn't on screen is searched for by scrolling through the content first. Returns a mini-diff of what the tap changed. |
| type_textB | Type text into the focused field (optionally tap a field first via ref/selector). submit presses Enter/Return. |
| swipeC | Swipe in a direction (from screen center) or between explicit points. |
| press_buttonB | Press a device button (home, back [Android], volumeUp, volumeDown, enter). |
| handle_alertA | Accept or dismiss a blocking alert/dialog (system permission prompts, 'Open in …?' sheets, in-app modals). Finds the right button from the current UI tree — no coordinates needed. Use buttonText for a specific button. Returns what was tapped and what changed; if no alert is present you get the current tree. |
| screenshotA | PNG screenshot — the fallback for purely visual checks (colors, images, layout polish). For text/structure, prefer get_ui_tree or wait_for: cheaper and more precise. |
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
Each tool has a distinct purpose: tapping, typing, swiping, waiting, etc. No two tools overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (e.g., wait_for, get_ui_tree). No mixing of conventions.
13 tools is well-scoped for mobile UI testing, covering all necessary actions without excess.
Covers core workflows like launching, interacting, waiting, and inspecting UI. Minor gaps like missing explicit scroll or long press, but swipe can compensate.