Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Available SDKs

xcodebuild-showsdks
Read-onlyIdempotent

List available Apple platform SDKs from your Xcode installation as structured JSON to verify SDK availability before builds and validate CI/CD environments.

Instructions

xcodebuild-showsdks

⚡ Show available SDKs for iOS, macOS, watchOS, and tvOS

What it does

Lists all SDKs available in your Xcode installation for building apps across Apple platforms. Returns structured JSON data instead of raw CLI text, making it easy to parse and validate SDK availability. Smart caching prevents redundant SDK queries, improving performance for repeated lookups. Validates Xcode installation before execution.

Why you'd use it

  • Verify SDK availability before starting builds (prevent build failures)

  • Discover which platform versions are supported by your Xcode installation

  • Validate CI/CD environment has required SDKs installed

  • Get structured SDK data for automated build configuration

Parameters

Optional

  • outputFormat (string, default: 'json'): "json" or "text" output format

Returns

Structured JSON containing all available SDKs organized by platform (iOS, macOS, watchOS, tvOS). Each SDK entry includes platform name, version, and SDK identifier. Smart caching reduces query overhead for repeated lookups.

Examples

Get available SDKs as JSON

const sdks = await xcodebuildShowSDKsTool({ outputFormat: "json" });

Get raw text output

const sdksText = await xcodebuildShowSDKsTool({ outputFormat: "text" });

Related Tools

  • xcodebuild-version: Get Xcode version information

  • xcodebuild-build: Build with specific SDK

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputFormatNojson

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.1.0
  2. Removedv1.1.0
  3. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses behaviors beyond the annotations: smart caching prevents redundant queries, Xcode installation is validated before execution, and structured JSON is returned instead of raw CLI text. No contradiction with the readOnlyHint, idempotentHint, or destructiveHint annotations.

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

Conciseness4/5

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

The description is well-organized with clear headings, bullet points, examples, and related tools. It is somewhat verbose and repeats the caching/JSON points, but the structure and front-loading make it easy for an agent to scan.

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?

Given the tool has only one optional parameter aided by enum values, no output schema, and strong annotations, the description is complete. It explains what the return data contains, provides examples, and covers relevant behavior like caching and validation.

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

Parameters4/5

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

The input schema has zero description coverage for the single parameter, but the description compensates with a dedicated Parameters section explaining outputFormat accepts 'json' or 'text', defaults to 'json', and provides examples. The meaning is clear and complete for the parameter's simple nature.

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 states a specific verb and resource: 'Show available SDKs' and lists SDKs for iOS, macOS, watchOS, and tvOS. It clearly differentiates from related tools like xcodebuild-version and xcodebuild-build by focusing on SDK enumeration.

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 provides clear use cases such as verifying SDK availability, discovering supported platform versions, and validating CI environments. It does not explicitly state when not to use it or provide exclusion conditions versus siblings, so it falls short of a full 5.

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

Deploy Server

Other Tools