How do I install the MCP skill?

Run npx skillmds@latest add alemar11/mcp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the MCP skill do?

Launch or diagnose Apple’s native headless Xcode MCP server on macOS. It is listed under AI & ML on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with MCP?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

alemar11 (@alemar11) published this skill. Their other Agent Skills are listed on their SkillMD profile.

MCP by alemar11 — Agent Skill

Name: MCP
Author: alemar11

File contents

Xcode MCP

Safely prepare, start, and verify the headless MCP server shipped with Xcode. This skill operates Apple's xcrun mcp-server; it does not install or substitute XcodeBuildMCP, configure an MCP client, or perform general Apple platform development work.

State model

Before interpreting status or choosing a launch branch, read the canonical state model. Keep the selected Xcode, permission state, server state, agent authorization, and launch outcome distinct.

When setup provenance or command safety is disputed, read sources. The selected Xcode's live help remains execution authority.

Discovery gate

Confirm the host is macOS and resolve the active Xcode with xcodebuild -version and xcode-select -p. When the user identifies another installed Xcode, scope DEVELOPER_DIR to every command and pass it explicitly inside elevated commands. Do not change global xcode-select unless requested.

Run xcrun --find mcp-server for that Xcode. On failure, immediately return unsupported with the exact Xcode and developer directory. Stop here: do not run any other mcp-server command or substitute another MCP implementation.

Supported preflight

Continue only after launcher discovery succeeds.

Inspect xcrun mcp-server --help and confirm that the selected Xcode supports every command or flag required by the chosen branch.
Run xcrun mcp-server status before changing anything. If the server is already running, return already-running with the observed state.
Classify the environment as attended-local, unattended-host, or isolated-ci. Default to attended-local; never infer isolated-ci.
Read launch workflows, then use only the selected branch. Obtain explicit approval immediately before administrator enablement, persistent agent or folder approval, or unsafe global authorization. Never use unsafe global authorization outside an explicitly identified disposable, isolated CI machine.

Verification and recovery

Treat the final status readback as launch evidence; an accepted command is not proof that the server is running.
If start fails, inspect current status and use xcrun mcp-server show-logs when the selected Xcode supports it. Do not retry enablement or persistent approval speculatively.
Do not stop or disable a successfully launched server unless the user asks.
Report the selected Xcode version and developer directory, environment, permission state, server state, agent authorization, exact commands run, and canonical launch_outcome.

---name: mcpdescription: Launch or diagnose Apple’s native headless Xcode MCP server on macOS.---# Xcode MCPSafely prepare, start, and verify the headless MCP server shipped with Xcode.This skill operates Apple's `xcrun mcp-server`; it does not install orsubstitute XcodeBuildMCP, configure an MCP client, or perform general Appleplatform development work.## State modelBefore interpreting status or choosing a launch branch, read the canonical[state model](references/states.md). Keep the selected Xcode, permission state,server state, agent authorization, and launch outcome distinct.When setup provenance or command safety is disputed, read[sources](references/sources.md). The selected Xcode's live help remainsexecution authority.## Discovery gateConfirm the host is macOS and resolve the active Xcode with`xcodebuild -version` and `xcode-select -p`. When the user identifies anotherinstalled Xcode, scope `DEVELOPER_DIR` to every command and pass it explicitlyinside elevated commands. Do not change global `xcode-select` unless requested.Run `xcrun --find mcp-server` for that Xcode. On failure, immediately return`unsupported` with the exact Xcode and developer directory. Stop here: do notrun any other `mcp-server` command or substitute another MCP implementation.## Supported preflightContinue only after launcher discovery succeeds.1. Inspect `xcrun mcp-server --help` and confirm that the selected Xcode supports every command or flag required by the chosen branch.2. Run `xcrun mcp-server status` before changing anything. If the server is already running, return `already-running` with the observed state.3. Classify the environment as `attended-local`, `unattended-host`, or `isolated-ci`. Default to `attended-local`; never infer `isolated-ci`.4. Read [launch workflows](references/launch-workflows.md), then use only the selected branch. Obtain explicit approval immediately before administrator enablement, persistent agent or folder approval, or unsafe global authorization. Never use unsafe global authorization outside an explicitly identified disposable, isolated CI machine.## Verification and recovery- Treat the final status readback as launch evidence; an accepted command is not proof that the server is running.- If start fails, inspect current status and use `xcrun mcp-server show-logs` when the selected Xcode supports it. Do not retry enablement or persistent approval speculatively.- Do not stop or disable a successfully launched server unless the user asks.- Report the selected Xcode version and developer directory, environment, permission state, server state, agent authorization, exact commands run, and canonical `launch_outcome`.

Frequently asked questions

MCP