Xcode MCP Server

MCP Server for executing shell commands from MCP clients, particularly useful for Xcode-related operations

Local serverstdio

What is the Xcode MCP MCP server?

Xcode mcp mcp server lets Claude, Cursor and other MCP clients work with Xcode MCP directly. MCP Server for executing shell commands from MCP clients, particularly useful for Xcode-related operations.

What Xcode MCP does

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.

Key capabilities

  • 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

Tools it exposes

Once connected, the assistant can call this tool directly:

  • Requirements — The Requirements tool exposed by this server

Installing the xcode mcp mcp server

The server is distributed via npm as @devyhan/xcode-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

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)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Xcode MCP sits in that group, and the shape of its toolset — Requirements — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • Maintained by devyhan.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the xcode mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
RequirementsThe Requirements tool exposed by this server.

How to install the Xcode MCP MCP server

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

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • 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)

Example prompts to try

  • Use Xcode MCP to Requirements.

Frequently asked questions

It connects Xcode MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Requirements) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Xcode MCP directly.