Skip to main content
Glama
Sign In
Xcode MCP Server

Xcode MCP Server

by PolarVista
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

run_xcrun

Execute Xcode tools via xcrun to build, test, and manage iOS/macOS development projects through a standardized interface.

Instructions

Executes a specified Xcode tool via 'xcrun'.

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": {
      "tool": "<tool>"
    },
    "name": "run_xcrun"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesName of the Xcode tool to execute.
argumentsNoOptional additional arguments to pass to the specified tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose execution environment, error handling, permissions needed, or output format, which are critical for a command execution 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 with zero waste, front-loading the core action. It's appropriately sized for the tool's scope, making it easy to parse quickly.

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?

Given the complexity of executing Xcode tools, lack of annotations, and no output schema, the description is incomplete. It doesn't cover execution context, result handling, or error cases, leaving significant gaps for an agent to use it correctly.

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 the two parameters. The description adds no additional meaning beyond implying execution via 'xcrun', which is minimal value over the schema's details.

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 verb ('executes') and resource ('a specified Xcode tool via xcrun'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'run_lldb' or 'run_tests' which also execute commands, missing full distinction.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites like having Xcode installed, or compare to siblings like 'run_lldb' for debugging or 'run_tests' for testing, leaving usage context unclear.

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