keyboard-ext-ax-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVELOPER_DIR | No | Path to the Xcode developer directory. Used to select a specific Xcode installation when multiple are present. Example: /Applications/Xcode.app/Contents/Developer |
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 |
|---|---|
| keyboard_snapshotA | Return the active keyboard extension accessibility tree and tap coordinates. The client app must already be foreground with a focused text field presenting the requested extension. The first call builds and starts cached XCTest support; later calls reuse the simulator session. |
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 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.