keyboard-ext-ax-mcp
Related Servers
Alternatives to keyboard-ext-ax-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to inspect the iOS Simulator's screen as compact text and perform real touch gestures, typing, assertions, and device controls without requiring testIDs.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to instantly read iOS Simulator frames and detect screen changes as text, eliminating slow screenshot round-trips.244 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables mirroring and controlling the iOS Simulator from MCP clients, providing a live viewer, agent cursor tracking, and token-efficient UI snapshots for automation.550 PyPI2Apache 2.0
- AlicenseAqualityAmaintenanceEnables driving an iOS Simulator from a model: taking screenshots, reading the UI tree, tapping, swiping, typing, managing app lifecycle and device state such as appearance, permissions, location, and notifications, without code signing or a physical device.25235 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural-language remote control and automation of iPads/iPhones over HTTPS, including app launching, accessibility inspection, taps, swipes, typing, device-local gesture sequences, and screenshot capture through a WebDriverAgent runner and cloud queue.MIT
- AlicenseNot gradedqualityCmaintenanceEnables controlling Android phones, emulators, and the iOS Simulator through the accessibility tree, offering compact snapshots, stable element refs, action diffs, and tools for tapping, typing, swiping, screenshots, and element discovery.Apache 2.0
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another. The tool's purpose is clearly stated in its name and description.
The single tool name 'keyboard_snapshot' follows a clear noun_verb style and is descriptive. However, with only one tool there is no broader pattern to evaluate for consistency.
A single tool for a keyboard extension accessibility server feels too thin for the apparent scope. Typical interaction would require additional actions like typing, tapping, or dismissing the keyboard.
The server provides only a snapshot/read operation with no corresponding actions or lifecycle coverage. Significant gaps exist for any real keyboard extension testing workflow.