keyboard-ext-ax-mcp
Related Servers
Alternatives to keyboard-ext-ax-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to instantly read iOS Simulator frames and detect screen changes as text, eliminating slow screenshot round-trips.690 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.2Apache 2.0
- AlicenseAqualityBmaintenanceEnables 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.216 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that drives the iOS Simulator via accessibility-tree snapshots with stable element refs, enabling LLMs to interactively find, tap, type, and inspect UI elements at sub-200ms latency.22 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables macOS GUI automation via screenshots, mouse/keyboard control, accessibility tree inspection, and app/window management.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect and verify mobile UI hierarchies, nodes, styles, screenshots, and runtime attributes of iOS apps in simulators or on USB devices.261 npm2Apache 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.