Xcode MCP Server

Overview Schema Source Related Servers Discussions Admin

xcode_create_project

Create a new Xcode project with basic structure by specifying project path, name, bundle identifier, and target platform (iOS/macOS).

Instructions

Create a new Xcode project with basic structure

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_path": "<project_path>",
      "project_name": "<project_name>",
      "bundle_id": "<bundle_id>"
    },
    "name": "xcode_create_project"
  }
}

Input Schema

Name	Required	Description	Default
`project_path`	Yes	Path where the project should be created
`project_name`	Yes	Name of the project
`bundle_id`	Yes	Bundle identifier (e.g., com.company.app)
`platform`	No	Target platform (ios/macos)	ios

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it creates a project with 'basic structure' but doesn't specify what that entails (e.g., default files, configurations), whether it overwrites existing projects, requires specific permissions, or handles errors. This leaves significant gaps for a mutation tool.

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 a single, efficient sentence that front-loads the core action and resource. There's no wasted wording, and it directly communicates the tool's purpose without unnecessary details.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., what 'basic structure' means, side effects), and while the schema covers parameters well, the overall context for safe and effective use is insufficient.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents all parameters. The description doesn't add any meaning beyond what the schema provides (e.g., it doesn't clarify 'basic structure' in relation to parameters). With high schema coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract.

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

Purpose4/5

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

The description clearly states the action ('Create') and resource ('new Xcode project with basic structure'), making the purpose immediately understandable. It doesn't specifically differentiate from sibling tools like 'xcode_create_directory' or 'xcode_create_swift_file' beyond mentioning 'project' versus 'directory' or 'file', which provides some distinction but not explicit comparison.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when not to use it, or compare it to sibling tools like 'xcode_create_directory' for creating project components separately. Usage is implied by the name and description alone.

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