Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@roeybiran/xcodebuild-mini-mcp) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

XcodeBuild Mini MCP Server

An MCP (Model Context Protocol) server that provides Xcode build operations through the MCP interface, following the official MCP Node.js guide.

Features

This MCP server provides the following tools:

build - Build an Xcode scheme
list_tests - List all tests for an Xcode scheme
build_tests - Build tests for an Xcode scheme
run_tests - Run tests for an Xcode scheme (with optional test filtering)
list_packages - List all packages in the Xcode project

Installation

Install dependencies:

npm install

Build the TypeScript code:

npm run build

Usage

Running the MCP Server

npm start

Or for development:

npm run dev

MCP Client Configuration

To use this MCP server with an MCP client, add it to your client configuration:

{
  "mcpServers": {
    "xcodebuild-mini": {
      "command": "npx",
      "args": ["-y", "@roeybiran/xcodebuild-mini-mcp"],
    }
  }
}

Available Tools

build

Build an Xcode scheme.

Parameters:

scheme (required): The Xcode scheme to build
warn (optional): Show warnings in output (default: false)

Example:

{
  "name": "build",
  "arguments": {
    "scheme": "MyApp",
    "warn": true
  }
}

list_tests

List all tests for an Xcode scheme.

Parameters:

scheme (required): The Xcode scheme to list tests for

Example:

{
  "name": "list_tests",
  "arguments": {
    "scheme": "MyApp"
  }
}

build_tests

Build tests for an Xcode scheme.

Parameters:

scheme (required): The Xcode scheme to build tests for

Example:

{
  "name": "build_tests",
  "arguments": {
    "scheme": "MyApp"
  }
}

run_tests

Run tests for an Xcode scheme.

Parameters:

scheme (required): The Xcode scheme to run tests for
only (optional): Run only specific test

Example:

{
  "name": "run_tests",
  "arguments": {
    "scheme": "MyApp",
    "only": "MyAppTests/testExample"
  }
}

list_packages

List all packages in the Xcode project.

Parameters: None

Example:

{
  "name": "list_packages",
  "arguments": {}
}

Requirements

Node.js 18+
Xcode command line tools
The xcodebuild command must be available in PATH

Development

Project Structure

xcodebuild-mini-mcp/
├── src/
│   ├── index.ts          # Main MCP server implementation (following MCP guide patterns)
│   └── xcodebuild.ts     # TypeScript implementation of Xcode build operations
├── dist/                 # Compiled JavaScript output
├── package.json          # Node.js dependencies
├── tsconfig.json         # TypeScript configuration
└── README.md            # This file

Implementation Details

This server follows the official MCP Node.js guide patterns:

Server Initialization: Uses the recommended Server class from @modelcontextprotocol/sdk
Transport: Uses StdioServerTransport for stdio-based communication
Tool Handlers: Implements ListToolsRequestSchema and CallToolRequestSchema handlers
Error Handling: Proper error handling with structured responses
Logging: Uses console.error for logging (stdout is reserved for JSON-RPC messages)

Building

npm run build

Development Mode

npm run dev

Error Handling

The MCP server handles errors gracefully and returns structured error responses. Common error scenarios include:

Invalid scheme names
Build failures
Test execution failures
Missing dependencies

All errors are returned with descriptive messages and proper error flags.

License

MIT