MCP Xcode
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_simulatorsC | List available iOS simulators |
| boot_simulatorC | Boot a simulator |
| shutdown_simulatorC | Shutdown a simulator |
| build_xcodeC | Build an Xcode project or workspace |
| install_appC | Install an app on the simulator |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: booting, building, installing, listing, and shutting down are all separate operations in the Xcode/simulator workflow. An agent can easily distinguish between them based on their specific actions.
All tools follow a consistent verb_noun pattern (e.g., boot_simulator, build_xcode, install_app), using snake_case throughout. This predictable naming makes the tool set easy to navigate and understand.
With 5 tools, the server is well-scoped for managing Xcode projects and simulators. Each tool serves a clear, essential function in this domain, avoiding bloat or thin coverage.
The tool set covers core operations for building and simulator management, but minor gaps exist, such as running tests or configuring project settings. However, agents can likely work around these with the provided tools for basic workflows.