Xcode MCP Server
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 |
|---|---|
| xcode_list_simulatorsB | List all available iOS, watchOS, and tvOS simulators |
| xcode_list_available_simulatorsA | List only available (not shutdown) simulators |
| xcode_list_simulators_jsonB | List simulators in JSON format for parsing |
| xcode_boot_simulatorC | Boot a specific simulator by device ID |
| xcode_shutdown_simulatorC | Shutdown a specific simulator |
| xcode_erase_simulatorC | Erase simulator data and settings |
| xcode_list_schemesB | List available schemes in an Xcode project |
| xcode_list_workspace_schemesC | List schemes in an Xcode workspace |
| xcode_build_projectC | Build an Xcode project with specific scheme and configuration |
| xcode_test_projectC | Run tests for an Xcode project |
| xcode_clean_projectC | Clean build artifacts for an Xcode project |
| xcode_archive_projectC | Create an archive for distribution |
| xcode_show_build_settingsC | Show build settings for a project/scheme |
| xcode_install_app_simulatorC | Install an app on a simulator |
| xcode_launch_app_simulatorC | Launch an app on a simulator |
| xcode_capture_screenshotC | Capture screenshot from simulator |
| xcode_show_sdk_infoB | Show available SDKs and their paths |
| xcode_show_destinationsB | Show available destinations for a scheme |
| xcode_create_swift_fileC | Create a new Swift source file with content |
| xcode_create_projectC | Create a new Xcode project with basic structure |
| xcode_modify_plistC | Modify a value in a plist file |
| xcode_add_plist_entryC | Add a new entry to a plist file |
| xcode_create_directoryC | Create a directory with subdirectories if needed |
| xcode_read_fileC | Read contents of a file |
| xcode_list_physical_devicesB | List all connected physical iOS devices |
| xcode_list_device_pairsB | List paired devices (iOS devices paired with Mac) |
| xcode_device_infoB | Get detailed information about a specific device |
| xcode_install_app_deviceB | Install an app on a physical device |
| xcode_build_for_deviceA | Build project specifically for physical device with automatic signing |
| xcode_run_on_deviceC | Build and run app on physical device |
| start_web_monitorB | Start the web interface for visual command execution and monitoring |
| stop_web_monitorB | Stop the web interface if it is running |
| web_monitor_statusB | Get the current status of the web monitor |
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 33 tools
Most tools have distinct purposes targeting specific Xcode operations like building, testing, simulator management, or file manipulation. However, some overlap exists: 'xcode_list_simulators' and 'xcode_list_available_simulators' could be confusing, and 'xcode_build_project' vs 'xcode_build_for_device' might cause misselection without careful reading of descriptions.
Tool names follow a highly consistent pattern: all start with 'xcode_' prefix (except three web monitor tools) and use snake_case with clear verb_noun structure (e.g., 'xcode_build_project', 'xcode_list_simulators'). The three web monitor tools also maintain consistent naming ('start_web_monitor', etc.).
With 33 tools, this is borderline heavy for an Xcode server. While Xcode has many functionalities, the count feels excessive and could overwhelm agents. Some tools might be consolidated (e.g., multiple simulator listing tools). A more focused set of 15-25 tools would be better scoped.
The toolset provides comprehensive coverage of Xcode development workflows: project creation, building, testing, archiving, simulator/device management, file operations, and monitoring. It includes CRUD-like operations for files and simulators, and covers both physical devices and simulators. No obvious gaps are present for the domain.