Skip to main content
Glama
Sign In
Xcode MCP Server

Xcode MCP Server

by PolarVista
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_project_path

Set the active Xcode project by specifying the path to its .xcodeproj directory, enabling AI assistants to build and test projects through the Xcode MCP Server.

Instructions

Sets the active Xcode project by specifying the path to its .xcodeproj directory.

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": {
      "projectPath": "<projectPath>"
    },
    "name": "set_project_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesPath to the .xcodeproj directory for the desired project.

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 basic action without behavioral details. It doesn't disclose whether this changes global state, requires specific permissions, has side effects (e.g., loading project settings), or what happens on failure (e.g., invalid path). For a mutation tool with zero annotation coverage, this is a significant gap.

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 directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, 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 tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It lacks details on behavioral traits, error handling, or output expectations, which are crucial for an agent to use it correctly in an Xcode context.

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%, with the single parameter 'projectPath' fully documented in the schema as 'Path to the .xcodeproj directory for the desired project.' The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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 ('Sets') and the resource ('active Xcode project'), specifying it requires a path to a .xcodeproj directory. It distinguishes from siblings like 'get_active_project' by indicating a setter function, but doesn't explicitly contrast with 'set_projects_base_dir' which might handle a different type of path setting.

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 (e.g., needing an Xcode environment), when not to use it, or how it relates to siblings like 'set_projects_base_dir' or 'get_active_project' for context switching.

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