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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-projectsA | Find all Xcode projects (.xcodeproj) in a directory. Searches recursively up to 5 levels deep, excluding common build directories. |
| read-projectB | Read and parse an Xcode project file (.xcodeproj). Returns project structure including targets, build configurations, and source files. |
| list-targetsB | List all build targets in an Xcode project with their product types (app, framework, test, etc.) |
| list-schemesB | List all schemes available in an Xcode project (both shared and user schemes) |
| buildC | Build an Xcode project using xcodebuild. Can specify target, scheme, configuration, and destination. |
| xcodebuild-infoB | Get xcodebuild version and available SDKs information |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: building projects, listing projects/schemes/targets, reading project details, and getting xcodebuild info. The descriptions reinforce these distinct roles, making misselection unlikely.
Most tools follow a consistent verb_noun pattern (list-projects, list-schemes, list-targets, read-project), but 'build' and 'xcodebuild-info' deviate slightly. The naming is still readable and predictable overall, with only minor inconsistencies.
Six tools is well-scoped for an Xcode server, covering essential operations like building, listing, reading, and getting system info. Each tool earns its place without feeling excessive or insufficient for the domain.
The toolset covers core Xcode workflows well, including discovery, inspection, and building. Minor gaps exist, such as no explicit tools for running tests or managing dependencies, but agents can likely work around these with the provided tools.