Xcode MCP Docs
Overview
Use Apple Xcode MCP documentation search for Apple platform API questions. This is the preferred source for current Apple Developer Documentation when answering Xcode, Swift, SwiftUI, UIKit, AppKit, Foundation, concurrency, and framework-specific questions.
Tool Availability
Before calling MCP tools, confirm the mcp__xcode namespace is available. If DocumentationSearch is not visible, use tool_search with DocumentationSearch Xcode MCP to expose the Apple documentation search tool. If the tool still is not available, tell the user Xcode MCP documentation search is not connected and stop rather than fabricating current Apple documentation.
Workflow
- Identify the API, framework, or behavior the user is asking about.
- Call
mcp__xcode.DocumentationSearch with a concise semantic query.
- Pass
frameworks when the framework is known, such as SwiftUI, UIKit, Foundation, AppKit, or Combine.
- If the first result set is too broad, refine the query with the API name, platform, and task.
- Use documentation results to guide code edits, diagnostics, snippets, or previews when relevant.
Query Guidance
- Prefer API/task queries such as
NavigationStack programmatic navigation SwiftUI over vague terms.
- Include framework filters when the same symbol name exists across frameworks.
- For migration or deprecation questions, include the target platform or replacement API.
- For code changes, pair documentation search with
$xcode-mcp-files and $xcode-mcp-edit rather than relying on docs alone.
Reporting
- Summarize the relevant Apple guidance in your own words.
- Name the framework/API used.
- If documentation results are inconclusive, say that and recommend checking the exact SDK/Xcode version in the project.
1---2name: xcode-mcp-docs3description: Search Apple Developer Documentation through Apple Xcode MCP semantic documentation search. Use when the user asks for Apple platform API guidance, framework usage, Swift/SwiftUI/UIKit/AppKit documentation, current Apple docs, or how an Apple API should be used from Xcode context.4---56# Xcode MCP Docs78## Overview910Use Apple Xcode MCP documentation search for Apple platform API questions. This is the preferred source for current Apple Developer Documentation when answering Xcode, Swift, SwiftUI, UIKit, AppKit, Foundation, concurrency, and framework-specific questions.1112## Tool Availability1314Before calling MCP tools, confirm the `mcp__xcode` namespace is available. If `DocumentationSearch` is not visible, use `tool_search` with `DocumentationSearch Xcode MCP` to expose the Apple documentation search tool. If the tool still is not available, tell the user Xcode MCP documentation search is not connected and stop rather than fabricating current Apple documentation.1516## Workflow17181. Identify the API, framework, or behavior the user is asking about.192. Call `mcp__xcode.DocumentationSearch` with a concise semantic query.203. Pass `frameworks` when the framework is known, such as `SwiftUI`, `UIKit`, `Foundation`, `AppKit`, or `Combine`.214. If the first result set is too broad, refine the query with the API name, platform, and task.225. Use documentation results to guide code edits, diagnostics, snippets, or previews when relevant.2324## Query Guidance2526- Prefer API/task queries such as `NavigationStack programmatic navigation SwiftUI` over vague terms.27- Include framework filters when the same symbol name exists across frameworks.28- For migration or deprecation questions, include the target platform or replacement API.29- For code changes, pair documentation search with `$xcode-mcp-files` and `$xcode-mcp-edit` rather than relying on docs alone.3031## Reporting3233- Summarize the relevant Apple guidance in your own words.34- Name the framework/API used.35- If documentation results are inconclusive, say that and recommend checking the exact SDK/Xcode version in the project.
ai-x-builder