What can you do with this server?

The Xcode MCP Server provides tools for managing and interacting with Xcode projects, simulators, and physical devices: * Project Management: Retrieve detailed information about Xcode projects/workspaces including targets, configurations, and schemes * Build Operations: Build projects with options for clean builds, custom output directories, and specific configurations * Testing: Run tests with granular control over test execution, including specific tests, test plans, and result bundles * Archiving & Distribution: Create archives and export them as IPA files for App Store, ad-hoc, or enterprise distribution * Code Signing: Manage signing identities and provisioning profiles, retrieving detailed information about both * Swift Package Integration: Access Swift Package Manager functions (initialize, update, resolve, reset, clean) * Simulator Management: Control iOS Simulators to list, create, boot, shutdown, erase, install apps, launch, and delete * Device Deployment: Deploy and run apps on physical iOS devices with support for device selection, environment variables, and log streaming

Which integrations are available for this server?

Supports app archiving and IPA export for App Store distribution through export options plist integration Enables iOS app deployment, testing on iOS simulators, and launching apps on physical iOS devices with log streaming capabilities Provides macOS-specific tooling for Xcode project management and iOS development workflows Offers Swift Package Manager integration for managing Swift packages with commands like init, update, resolve, reset, and clean Provides tools for Xcode project management, building, testing, archiving, code signing, and related iOS development operations

How do I use Xcode MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Xcode MCP Server build my project for iPhone 14 simulator" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

en es ja ko zh

Xcode MCP Server

by devyhan

Overview Schema Related Servers Score Discussions

JavaScript

Local

xcode-mcp

An MCP (Model Context Protocol) server that provides tools for Xcode-related operations, making it easier to work with Xcode projects from MCP clients like Claude Desktop. The server offers various utilities for Xcode project management, building, testing, archiving, code signing, and related iOS development tools.

Features

Xcode project information retrieval and scheme listing
Enhanced build capabilities with clean and custom output options
Comprehensive test execution with granular control
App archiving and IPA export for distribution
Code signing and provisioning profile management
Swift Package Manager integration
iOS Simulator management via simctl
NEW: Real Device App Deployment and Launch with automatic Xcode installation detection and improved device management
Intelligent handling of app installation failures with auto-retry
Smart caching of device and Xcode information for better performance

Related MCP server: sl-test

Installation

npm install @devyhan/xcode-mcp

Usage

Using with Claude Desktop

Open Claude Desktop config file:

# macOS
open ~/Library/Application\ Support/Claude/claude_desktop_config.json

Add or modify the following configuration:

{
  "mcpServers": {
    "xcode-mcp": {
      "command": "npx",
      "args": [
        "@devyhan/xcode-mcp",
        "-y"
      ]
    }
  }
}

Restart Claude Desktop.

Available Tools

1. xcode-project-info

Retrieves detailed information about an Xcode project or workspace, including targets, configurations, and schemes.

Parameters:

projectPath (required): Path to the Xcode project (.xcodeproj) or workspace (.xcworkspace)

Example:

Project path: /Users/username/Projects/MyApp/MyApp.xcodeproj

Sample Output:

{
  "project": {
    "name": "MyApp",
    "targets": ["MyApp", "MyAppTests", "MyAppUITests"],
    "configurations": ["Debug", "Release"],
    "schemes": ["MyApp"]
  }
}

2. xcode-list-schemes

Provides a comprehensive list of all available schemes, targets, and configurations in an Xcode project or workspace.

Parameters:

projectPath (required): Path to the Xcode project (.xcodeproj) or workspace (.xcworkspace)

Example:

Project path: /Users/username/Projects/MyApp/MyApp.xcodeproj

Sample Output:

Information about project "MyApp":
    Targets:
        MyApp
        MyAppTests
        MyAppUITests

    Build Configurations:
        Debug
        Release

    Schemes:
        MyApp
        MyAppTests

3. xcode-build

Builds an Xcode project or workspace with enhanced options. Supports both workspace and project builds, clean builds, and custom output directories.

Parameters:

projectPath (required): Path to the Xcode project (.xcodeproj) or workspace (.xcworkspace)
scheme (required): The scheme to build
configuration (optional): Build configuration (e.g., Debug, Release)
destination (optional): Build destination (e.g., 'platform=iOS Simulator,name=iPhone 14')
extraArgs (optional): Additional xcodebuild arguments as array of strings
outputDir (optional): Custom build output directory (SYMROOT)
clean (optional): Whether to perform clean build (default: false)

Example:

Project path: /Users/username/Projects/MyApp/MyApp.xcodeproj
Scheme: MyAppScheme
Configuration: Debug
Destination: platform=iOS Simulator,name=iPhone 14
Clean: true
OutputDir: /Users/username/Desktop/build

Command Generated:

xcodebuild -project "/Users/username/Projects/MyApp/MyApp.xcodeproj" -scheme "MyAppScheme" clean build -configuration "Debug" -destination "platform=iOS Simulator,name=iPhone 14" SYMROOT="/Users/username/Desktop/build"

4. xcode-test

Runs tests for an Xcode project or workspace with extensive options. Provides fine-grained control over test execution, including running specific tests, test plans, and various testing modes.

Parameters:

projectPath (required): Path to the Xcode project (.xcodeproj) or workspace (.xcworkspace)
scheme (required): The scheme to test
destination (required): Test destination (e.g., 'platform=iOS Simulator,name=iPhone 14')
testPlan (optional): Name of the test plan to use
onlyTesting (optional): Array of specific test identifiers to run
skipTesting (optional): Array of test identifiers to skip
resultBundlePath (optional): Path to save test result bundle
buildForTesting (optional): Build for testing only without running tests
testWithoutBuilding (optional): Run tests without building

Example:

Project path: /Users/username/Projects/MyApp/MyApp.xcodeproj
Scheme: MyAppScheme
Destination: platform=iOS Simulator,name=iPhone 14
OnlyTesting: ["MyAppTests/LoginTests"]
ResultBundlePath: /Users/username/Desktop/TestResults

Command Generated:

xcodebuild -project "/Users/username/Projects/MyApp/MyApp.xcodeproj" -scheme "MyAppScheme" -destination "platform=iOS Simulator,name=iPhone 14" test -only-testing:"MyAppTests/LoginTests" -resultBundlePath "/Users/username/Desktop/TestResults"

5. xcode-archive

Creates an archive (.xcarchive) of an Xcode project and optionally exports it to an IPA file for distribution. Supports App Store, ad-hoc, and enterprise distribution methods through export options plist.

Parameters:

projectPath (required): Path to the Xcode project (.xcodeproj) or workspace (.xcworkspace)
scheme (required): The scheme to archive
configuration (optional): Build configuration (e.g., Release)
archivePath (required): Path to save the .xcarchive file
exportPath (optional): Path to export the archive (e.g., IPA file)
exportOptionsPlist (optional): Path to the exportOptions.plist file

Example:

Project path: /Users/username/Projects/MyApp/MyApp.xcodeproj
Scheme: MyAppScheme
Configuration: Release
ArchivePath: /Users/username/Desktop/MyApp.xcarchive
ExportPath: /Users/username/Desktop/Export
ExportOptionsPlist: /Users/username/Projects/MyApp/exportOptions.plist

Commands Generated:

# Archive command
xcodebuild -project "/Users/username/Projects/MyApp/MyApp.xcodeproj" -scheme "MyAppScheme" -configuration "Release" archive -archivePath "/Users/username/Desktop/MyApp.xcarchive"

# Export command (if exportPath and exportOptionsPlist are provided)
xcodebuild -exportArchive -archivePath "/Users/username/Desktop/MyApp.xcarchive" -exportPath "/Users/username/Desktop/Export" -exportOptionsPlist "/Users/username/Projects/MyApp/exportOptions.plist"

6. xcode-codesign-info

Retrieves comprehensive code signing and provisioning profile information for an Xcode project. Shows installed code signing identities, project code signing settings, and provisioning profiles on the system.

Parameters:

projectPath (required): Path to the Xcode project (.xcodeproj) or workspace (.xcworkspace)
target (optional): Specific target name

Example:

Project path: /Users/username/Projects/MyApp/MyApp.xcodeproj
Target: MyAppTarget

Sample Output:

코드 서명 인증서 목록:
  1) 01AB2345CD6789EF0123456789ABCDEF01234567 "Apple Development: John Doe (ABC12DEF34)"
  2) 9876543210FEDCBA98765432109876543210FEDC "Apple Distribution: Example Corp (XYZ12ABC3)"

프로젝트 코드 서명 설정:
    CODE_SIGN_IDENTITY = Apple Development
    CODE_SIGN_STYLE = Automatic
    DEVELOPMENT_TEAM = ABC123DEF4
    PROVISIONING_PROFILE_SPECIFIER = 

설치된 프로비저닝 프로파일:
-rw-r--r--  1 username  staff  12345 Feb  1 12:34 01234567-89ab-cdef-0123-456789abcdef.mobileprovision
-rw-r--r--  1 username  staff  23456 Mar 15 09:12 fedcba98-7654-3210-fedc-ba9876543210.mobileprovision

7. swift-package-manager

Provides access to Swift Package Manager (SPM) functionality for managing Swift packages. Supports common SPM commands like init, update, resolve, reset, and clean.

Parameters:

command (required): SPM command to execute ("init", "update", "resolve", "reset", "clean")
packageDir (required): Directory path of the Swift Package
extraArgs (optional): Additional SPM arguments as array of strings

Example:

Command: update
PackageDir: /Users/username/Projects/MySwiftPackage
ExtraArgs: ["--enable-pubgrub-resolver"]

Command Generated:

cd "/Users/username/Projects/MySwiftPackage" && swift package update --enable-pubgrub-resolver

Sample Output:

Resolving dependencies...
Fetching https://github.com/example/example-package.git
Checking out https://github.com/example/example-package.git at 1.2.3

8. simctl-manager

Provides access to iOS Simulator management capabilities via the simctl command-line tool. Supports listing, creating, booting, installing apps, and managing simulator devices.

Parameters:

command (required): SimCtl command ("list", "create", "boot", "shutdown", "erase", "install", "launch", "delete")
extraArgs (optional): Additional simctl arguments as array of strings

Example:

Command: list
ExtraArgs: ["devices", "--json"]

Command Generated:

xcrun simctl list devices --json

Sample Output (abbreviated):

{
  "devices": {
    "com.apple.CoreSimulator.SimRuntime.iOS-17-0": [
      {
        "name": "iPhone 14",
        "udid": "12345678-1234-1234-1234-123456789ABC",
        "state": "Booted",
        "isAvailable": true
      }
    ]
  }
}

9. run-on-device

Builds, installs, and runs an app on a physical iOS device. Supports device name (including Korean names) or UUID for device selection, environment variables, and log streaming. Now with direct bundleId specification, skip build option, and additional launch arguments.

Parameters:

projectPath (required): Path to the Xcode project (.xcodeproj) or workspace (.xcworkspace)
scheme (required): The scheme to build and run
device (required): Device identifier or name (supports Korean names)
configuration (optional): Build configuration (e.g., Debug, Release)
streamLogs (optional): Whether to stream device logs after launching
startStopped (optional): Whether to start the app in a paused state for debugger attachment
environmentVars (optional): Environment variables to pass to the app (key1=value1,key2=value2 format)
xcodePath (optional): Xcode application path (default: "/Applications/Xcode-16.2.0.app")
listDevices (optional): Display all detected devices with their IDs before running
skipBuild (optional): Skip the build and install step for already installed apps
extraLaunchArgs (optional): Additional arguments to pass to the devicectl launch command
directBundleId (optional): Directly specify the bundle ID instead of extracting from project

Example:

Project path: /Users/username/Projects/MyApp/MyApp.xcodeproj
Scheme: MyAppScheme
Device: "Your-iPhone"
Configuration: Debug
StreamLogs: true
EnvironmentVars: "DEBUG_MODE=1,API_URL=https://test-api.example.com"

Process:

The tool identifies both Xcode UDID and CoreDevice UUID for the specified device
It uses the Xcode UDID for building and installing the app
It uses the CoreDevice UUID for launching the app with devicectl
It retrieves the app's bundle identifier
If requested, it streams the device logs

Key Improvements in v0.4.0:

Ability to specify bundleId directly without needing a project
Skip build and install step for already installed apps
Support for additional devicectl launch command arguments
Better device model and OS version information display
Improved path handling and logging for devicectl commands

Sample Output:

// Standard output with build and install
앱 실행 결과:
Launched application with com.example.myapp bundle identifier.
로그 스트리밍이 시작되었습니다. 로그는 터미널에서 확인할 수 있습니다.

// Direct bundle ID usage with skip build
기기 모델: iPhone14,7
기기 OS 버전: 17.0
사용자 지정 번들 ID 사용: com.example.myapp
빌드 및 설치 과정 건너뛰기
앱 실행 결과:
Launched application with com.example.myapp bundle identifier.

Example Scenario: Using with LLMs

Below is an example of how you might prompt an LLM like Claude to use these tools in sequence:

User Prompt to Claude:

I need to inspect my Xcode project, run some tests, and then archive it for distribution.

1. First, use the xcode-list-schemes tool to get all available schemes for my project at /Users/username/Projects/MyApp/MyApp.xcodeproj
2. After you see the schemes, run tests for the first available scheme on the iPhone 14 simulator.
3. Then archive the app for distribution using the Release configuration.

Expected Workflow:

Claude will execute the xcode-list-schemes tool to retrieve all schemes:
```
Project path: /Users/username/Projects/MyApp/MyApp.xcodeproj
```

Claude will execute the xcode-test tool with the identified scheme:

Project path: /Users/username/Projects/MyApp/MyApp.xcodeproj
Scheme: [First scheme from output]
Destination: platform=iOS Simulator,name=iPhone 14

Claude will then use the xcode-archive tool to create an archive:

Project path: /Users/username/Projects/MyApp/MyApp.xcodeproj
Scheme: [First scheme from output]
Configuration: Release
ArchivePath: /Users/username/Desktop/MyApp.xcarchive

This workflow demonstrates how to chain multiple tools together, using the output from one tool to inform the parameters for another.

Example: Running on a Real Device

User Prompt to Claude:

I need to test my app on a real device:

1. Get the list of available devices (including connected physical devices)
2. Run my app on my connected iPhone

Expected Workflow:

Claude will first get the list of devices:
```
listDevices: true
```

Claude will identify your physical device and run the app on it:

Project path: /Users/username/Projects/MyApp/MyApp.xcodeproj
Scheme: MyApp
Device: "Your iPhone" (or the device UUID)
StreamLogs: true

For quick re-launch without rebuilding:

Device: "Your iPhone"
DirectBundleId: "com.example.myapp"
SkipBuild: true

Security Considerations

This tool can execute Xcode-related commands, which poses security risks. Please note:

Only use with trusted Xcode projects.
Be cautious with projects from unknown sources.
Do not include sensitive information in build parameters.

Development

Requirements

Node.js 16 or higher
npm 6 or higher
Xcode 14 or higher (for all features)
Xcode 16 or higher (required for devicectl and real device features)

Local Development and Testing

# Clone the repository
git clone https://github.com/devyhan/xcode-mcp.git
cd xcode-mcp

# Install dependencies
npm install

# Run in development mode
npm run dev

# Build
npm run build

# Test
npm test

License

MIT

Available Tools

9 tools

run-on-deviceD

ParametersJSON Schema

Name	Required	Description
`projectPath`	Yes	Xcode 프로젝트 또는 워크스페이스 경로
`scheme`	Yes	빌드 및 실행할 스킴
`device`	Yes	기기 식별자 또는 이름 (한글 이름 지원)
`configuration`	No	빌드 구성 (Debug/Release)
`streamLogs`	No	앱 실행 후 로그 스트리밍 여부
`startStopped`	No	디버거 연결을 위한 일시 중지 상태로 시작
`environmentVars`	No	앱에 전달할 환경 변수 (key1=value1,key2=value2 형식)
`xcodePath`	No	Xcode 애플리케이션 경로
`listDevices`	No	실행 전 감지된 모든 디바이스 목록 표시
`skipBuild`	No	이미 설치된 앱을 재실행할 때 빌드 및 설치 건너뛰기
`extraLaunchArgs`	No	devicectl launch 명령어에 전달할 추가 인자
`directBundleId`	No	직접 지정할 번들 ID (프로젝트에서 추출하지 않음)

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

simctl-managerD

ParametersJSON Schema

Name	Required	Description	Default
`command`	Yes	SimCtl 명령어
`extraArgs`	No	추가 simctl 인자들

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

swift-package-managerD

ParametersJSON Schema

Name	Required	Description
`command`	Yes	SPM 명령어 (init, update, resolve, reset, clean)
`packageDir`	Yes	Swift Package 디렉토리 경로
`extraArgs`	No	추가 SPM 인자들

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

xcode-archiveD

ParametersJSON Schema

Name	Required	Description
`projectPath`	Yes	Xcode 프로젝트 또는 워크스페이스 경로
`scheme`	Yes	아카이브할 스킴
`configuration`	No	빌드 구성 (예: Release)
`archivePath`	Yes	아카이브 파일(.xcarchive) 저장 경로
`exportPath`	No	익스포트 경로 (IPA 파일 등)
`exportOptionsPlist`	No	익스포트 옵션 plist 파일 경로

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

xcode-buildD

ParametersJSON Schema

Name	Required	Description
`projectPath`	Yes	Xcode 프로젝트 또는 워크스페이스 경로
`scheme`	Yes	빌드할 스킴
`configuration`	No	빌드 구성 (예: Debug, Release)
`destination`	No	빌드 대상 (예: 'platform=iOS Simulator,name=iPhone 14')
`extraArgs`	No	추가 xcodebuild 인자들
`outputDir`	No	빌드 결과물 저장 경로 (SYMROOT)
`clean`	No	빌드 전 clean 실행 여부

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

xcode-codesign-infoD

ParametersJSON Schema

Name	Required	Description	Default
`projectPath`	Yes	Xcode 프로젝트 또는 워크스페이스 경로
`target`	No	특정 타겟 이름 (선택사항)

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

xcode-list-schemesD

ParametersJSON Schema

Name	Required	Description	Default
`projectPath`	Yes	Xcode 프로젝트 또는 워크스페이스 경로

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

xcode-project-infoD

ParametersJSON Schema

Name	Required	Description	Default
`projectPath`	Yes	Xcode 프로젝트 또는 워크스페이스 경로

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

xcode-testD

ParametersJSON Schema

Name	Required	Description
`projectPath`	Yes	Xcode 프로젝트 또는 워크스페이스 경로
`scheme`	Yes	테스트할 스킴
`destination`	Yes	테스트 대상 (예: 'platform=iOS Simulator,name=iPhone 14')
`testPlan`	No	사용할 테스트 플랜 이름
`onlyTesting`	No	실행할 특정 테스트 식별자들 (예: ['ModuleTests/ClassTests/testMethod'])
`skipTesting`	No	건너뛸 테스트 식별자들
`resultBundlePath`	No	테스트 결과 번들 저장 경로
`buildForTesting`	No	테스트용 빌드만 수행할지 여부
`testWithoutBuilding`	No	빌드 없이 테스트만 수행할지 여부

TDQS

D1/5.0

Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

9 tool updatesAug 18, 2025
- First observedrun-on-device
- First observedsimctl-manager
- First observedswift-package-manager
- First observedxcode-archive
- First observedxcode-build
- First observedxcode-codesign-info
- First observedxcode-list-schemes
- First observedxcode-project-info
- First observedxcode-test

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.8/5.0

Disambiguation4/5

Most tools have clearly distinct purposes targeting different Xcode workflows (building, testing, archiving, etc.), though 'simctl-manager' and 'run-on-device' could potentially overlap in device-related operations. The lack of descriptions makes it harder to fully assess boundaries, but the naming suggests reasonable separation.

Naming Consistency3/5

There's a mixed naming convention: most tools use a consistent 'xcode-' prefix with snake_case (e.g., 'xcode-build'), but 'simctl-manager', 'swift-package-manager', and 'run-on-device' deviate from this pattern. This inconsistency reduces predictability, though the names remain generally readable.

Tool Count5/5

With 9 tools, the count is well-scoped for an Xcode development server, covering key operations like building, testing, and project management. Each tool appears to serve a distinct function, avoiding both bloat and thin coverage for the domain.

Completeness3/5

The tools cover core development workflows (build, test, archive, etc.) but lack descriptions make it hard to assess gaps fully. Based on naming, there might be missing operations like code editing, debugging, or version control integration, which are common in Xcode environments, suggesting moderate incompleteness.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Appcircle MCP
io.appcircle
MCP server for Appcircle mobile CI/CD platform.
CI/CD & DevOps Developer Tools
2
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
237
l0-py-blocks-mcp A
io.github.SELISEdigitalplatforms
A Model Context Protocol (MCP) server for Selise Blocks Cloud integration
Cloud Platforms Developer Tools App Automation
362
AgentCloud — Hosted iOS Simulator MCP
so.agentcloud
Build, run, and inspect iOS apps in disposable hosted Simulators from cloud coding agents.
Code Execution Testing & QA Tools
1

Related MCP Servers

Xcode MCP Server
Developer Tools Testing & QA Tools Code Execution
PolarVista
A
license
B
quality
F
maintenance
A Model Context Protocol server that enables AI assistants to build and test Xcode projects directly through a standardized interface, with capabilities for running tests, monitoring progress, and accessing logs in real-time.
Updated 2 years ago (2024-12-06 15:41 UTC)
18
234
53
MIT
sl-test
Developer Tools CI/CD & DevOps Version Control
SampsonKY
A
license
B
quality
D
maintenance
A Model Context Protocol (MCP) server that provides Xcode-related tools for integration with AI assistants and other MCP clients.
Updated a year ago (2025-06-05 18:20 UTC)
54
178,423
1
MIT
MCP Xcode Server
Developer Tools Code Execution Command Line
chacebot
A
license
Not graded
quality
D
maintenance
An MCP server that provides tools for programmatically interacting with Xcode projects, enabling users to manage targets, schemes, and files. It supports essential development tasks including building, testing, and cleaning projects through the Xcode command-line tools.
Updated 7 months ago (2026-01-23 23:54 UTC)
41
MIT
simctl-mcp
Developer Tools Virtualization Testing & QA Tools
ambar
A
license
B
quality
D
maintenance
A Model Context Protocol server implementation for iOS Simulator control, providing tools for device management, app operations, permissions, system features, and certificate handling.
Updated a year ago (2025-08-22 05:31 UTC)
29
20
20
MIT

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/devyhan/xcode-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server