Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy

xcodebuild-build

Builds Xcode projects and workspaces with intelligent defaults that remember successful configurations and suggest optimal simulators, while tracking performance metrics and providing structured error messages.

Instructions

xcodebuild-build

Build Xcode projects with intelligent defaults and performance tracking

What it does

Builds Xcode projects and workspaces with advanced learning capabilities that remember successful configurations and suggest optimal simulators per project. Uses progressive disclosure to provide concise summaries by default, with full build logs available on demand. Tracks build performance metrics (duration, errors, warnings) and learns from successful builds to improve future build suggestions.

Why you'd use it

  • Automatic smart defaults: remembers which simulator and config worked last time

  • Progressive disclosure: concise summaries prevent token overflow, full logs on demand

  • Performance tracking: measures build times and provides optimization insights

  • Structured errors: clear error messages instead of raw CLI stderr

Parameters

Required

  • projectPath (string): Path to .xcodeproj or .xcworkspace file

  • scheme (string): Build scheme name (use xcodebuild-list to discover)

Optional

  • configuration (string, default: 'Debug'): Build configuration (Debug/Release, defaults to cached or "Debug")

  • destination (string): Build destination (e.g., "platform=iOS Simulator,id=")

  • sdk (string): SDK to build against (e.g., "iphonesimulator", "iphoneos")

  • derivedDataPath (string): Custom derived data path for build artifacts

Returns

Structured JSON response with buildId (for progressive disclosure), success status, build summary (errors, warnings, duration), and intelligence metadata showing which smart defaults were applied. Use xcodebuild-get-details with buildId to retrieve full logs.

Examples

Minimal build with smart defaults

const result = await xcodebuildBuildTool({
  projectPath: "/path/to/MyApp.xcodeproj",
  scheme: "MyApp"
});

Explicit configuration

const release = await xcodebuildBuildTool({
  projectPath: "/path/to/MyApp.xcworkspace",
  scheme: "MyApp",
  configuration: "Release",
  destination: "platform=iOS Simulator,id=ABC-123"
});
  • xcodebuild-test: Run tests after building

  • xcodebuild-clean: Clean build artifacts

  • xcodebuild-get-details: Get full build logs (use with buildId)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYes
schemeYes
configurationNoDebug
destinationNo
sdkNo
derivedDataPathNo
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description must disclose behavioral traits. It explains that the tool remembers successful configurations, uses progressive disclosure, tracks build metrics, and returns structured JSON with a buildId for log retrieval. It does not mention any destructive side effects or permissions, but for a build tool, the described behavior is transparent enough.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with markdown headings, emojis, and sections for purpose, benefits, parameters, returns, examples, and related tools. It is detailed but efficient, with every section providing necessary information. No redundant content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description thoroughly covers input parameters, return value structure, and how to retrieve full logs via another tool. It also mentions related tools and provides examples. For a complex tool with 6 parameters, this description is highly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining each parameter's purpose, defaults, and examples. Required parameters (projectPath, scheme) are clearly described, and optional parameters (configuration, destination, etc.) include usage context and defaults. The examples demonstrate typical use cases.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool builds Xcode projects with intelligent defaults and performance tracking. It differentiates itself from siblings like xcodebuild-test, xcodebuild-clean, and xcodebuild-get-details by highlighting its learning capabilities and progressive disclosure.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Why you'd use it' section lists key benefits (smart defaults, progressive disclosure, performance tracking, structured errors) and the 'Related Tools' section provides alternatives for different use cases (e.g., testing, cleaning, logs). While it doesn't explicitly state when not to use this tool, the guidance is sufficiently clear for an AI agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/conorluddy/xc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server