You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Autonomously fixing build errors in Cursor](#autonomously-fixing-build-errors-in-cursor)
37
36
-[Utilising the new UI automation and screen capture features](#utilising-the-new-ui-automation-and-screen-capture-features)
@@ -43,15 +42,6 @@ A Model Context Protocol (MCP) server that provides Xcode-related tools for inte
43
42
44
43
XcodeBuildMCP is a Model Context Protocol (MCP) server that exposes Xcode operations as tools for AI assistants and other MCP clients. Built with a modern plugin architecture, it provides 84 self-contained tools organized into workflow-based directories, enabling programmatic interaction with Xcode projects, simulators, devices, and Swift packages through a standardized interface.
45
44
46
-
### Architecture Highlights
47
-
48
-
-**Plugin Architecture**: Self-contained tools with automatic discovery and zero-config registration
49
-
-**Tool Granularity**: 84 specialized tools across 16 plugin directories for precise control
50
-
-**Dynamic Loading**: Automatic plugin discovery with flexible enablement options
-**Tool Implementation** (`src/tools/*.ts`): Individual tool logic with Zod validation
324
-
-**Utilities** (`src/utils/*.ts`): Shared functionality for command execution, error handling
325
-
-**Type System** (`src/types/common.ts`): Core interfaces and enums
326
-
327
-
### Testing Infrastructure
328
-
329
-
-**Framework**: Vitest with TypeScript support
330
-
-**Coverage**: 407 tests across 26 test files
331
-
-**Pattern**: Import production code, mock only external dependencies
332
-
-**Validation**: Deterministic response validation for all tools
333
-
334
-
For detailed architectural documentation, see [ARCHITECTURE.md](docs/ARCHITECTURE.md).
335
-
336
-
## Selective tool registration
337
-
338
-
By default all tools are enabled but for some clients it may be useful to only enable specific tools to reduce the amount of context that is sent to the client. This can be achieved by setting specific environment variables in your clients MCP configuration.
339
-
340
-
Once you have enabled one or more tools or groups of tools all other tools will be disabled. For example, to enable only the simulator related tools, you can set the environment variable to `XCODEBUILDMCP_GROUP_IOS_SIMULATOR_WORKFLOW=true` this will only expose tools for building, running and debugging on simulators
0 commit comments