Skip to main content
Glama
Sign In
Xcode MCP Server

Xcode MCP Server

by r-huijts
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_projects

Search a directory for Xcode projects, with options to include Swift Package Manager projects and Xcode workspaces.

Instructions

Finds Xcode projects in the specified directory.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryNoDirectory to search in. Defaults to projects base directory.
includeSPMNoIf true, include Swift Package Manager projects
includeWorkspacesNoIf true, include .xcworkspace files

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosure. It does not explain what exactly constitutes an Xcode project (e.g., .xcodeproj directories), whether the search is recursive, what the output format is, or how the includeSPM and includeWorkspaces parameters alter the default behavior.

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 sentence, direct and free of redundancy. It is appropriately sized for a simple tool and front-loads the core action and object.

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 lack of an output schema, the description does not explain what the tool returns (paths? names?), nor does it describe the impact of the optional parameters. The behavior of including/excluding workspaces and SPM packages is left entirely to the schema, which is insufficient for an agent to use the tool 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?

The schema provides complete descriptions for all three parameters, so the baseline is 3. The description adds no additional meaning beyond the existence of the directory parameter; it does not clarify the semantics or default values of includeSPM and includeWorkspaces.

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 states the specific action (finds) and resource (Xcode projects) with a location qualifier, clearly distinguishing it from generic file search tools like find_files. However, it doesn't explicitly mention that it can also include workspaces or Swift Package Manager projects, which are key differentiators.

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

Usage Guidelines3/5

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

The phrase 'in the specified directory' implies a scoped search, and the tool's purpose suggests it is for locating project roots before using tools like get_project_configuration. However, it lacks explicit guidance on when to prefer this over alternatives like find_files or list_directory, and no exclusion criteria are provided.

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