Get the FREE Ultimate OpenClaw Setup Guide →

ax-apple-docs

npx machina-cli add skill Kasempiternal/axiom-v2/ax-apple-docs --openclaw
Files (1)
SKILL.md
7.3 KB

Apple Docs & Xcode MCP

Quick Patterns

Xcode MCP Setup (Xcode 26.3+)

  1. Xcode Settings > Intelligence > Enable Model Context Protocol + Xcode Tools ON
  2. Add to your MCP client:
# Claude Code
claude mcp add --transport stdio xcode -- xcrun mcpbridge

# Codex
codex mcp add xcode -- xcrun mcpbridge
// Cursor (.cursor/mcp.json)
{ "mcpServers": { "xcode": { "command": "xcrun", "args": ["mcpbridge"] } } }

// VS Code (.vscode/mcp.json)
{ "servers": { "xcode": { "type": "stdio", "command": "xcrun", "args": ["mcpbridge"] } } }
  1. Verify: call XcodeListWindows -- should return tabIdentifier + workspacePath

Xcode MCP Tools (20 tools)

Discovery: XcodeListWindows -- call first, get tabIdentifier for all other tools

File Ops: XcodeRead, XcodeWrite, XcodeUpdate (str_replace patches), XcodeGlob, XcodeGrep, XcodeLS, XcodeMakeDir, XcodeRM (destructive), XcodeMV (destructive)

Build/Test: BuildProject(tabIdentifier), GetBuildLog(tabIdentifier), RunAllTests(tabIdentifier), RunSomeTests(tabIdentifier, tests), GetTestList(tabIdentifier)

Diagnostics: XcodeListNavigatorIssues(tabIdentifier) -- structured diagnostics, XcodeRefreshCodeIssuesInFile(tabIdentifier, path)

Other: ExecuteSnippet(code, language), RenderPreview(tabIdentifier, path, previewIdentifier), DocumentationSearch(query)

Xcode MCP Workflows

BuildFix Loop:

1. BuildProject(tab) -> check result
2. XcodeListNavigatorIssues(tab) -> structured diagnostics
3. XcodeUpdate(file, patches) -> fix errors
4. Repeat (max 5 iterations)

TestFix Loop:

1. GetTestList(tab) -> discover tests
2. RunSomeTests(tab, [failing]) -> fast iteration
3. XcodeUpdate -> fix
4. Repeat, then RunAllTests for verification

PreviewVerify: RenderPreview(tab, file, viewName) -> review image -> edit -> re-render

App Store Connect MCP (asc-mcp)

brew install mint && mint install zelentsov-dev/asc-mcp@1.4.0

claude mcp add asc-mcp \
  -e ASC_KEY_ID=YOUR_KEY_ID \
  -e ASC_ISSUER_ID=YOUR_ISSUER_ID \
  -e ASC_PRIVATE_KEY_PATH=/path/to/AuthKey.p8 \
  -- ~/.mint/bin/asc-mcp --workers apps,builds,versions,reviews

Worker presets: TestFlight (apps,builds,beta_groups,beta_testers), Release (apps,builds,versions,reviews), Monetization (apps,iap,subscriptions,offer_codes,pricing)

WWDC Transcript Research

Navigate to developer.apple.com/videos/play/wwdcYYYY/NNN/ with browser. Page contains full verbatim transcript with timestamps. Extract API names, code descriptions, chapter markers.

sosumi.ai for API Docs

Clean markdown version of Apple docs. URL: sosumi.ai/documentation/[framework] (lowercase, no spaces/hyphens).

sosumi.ai/documentation/swiftui
sosumi.ai/documentation/widgetkit
sosumi.ai/documentation/appintents
sosumi.ai/documentation/avfoundation

Decision Tree

Need Apple documentation?
+-- Compiler error/warning? --> Read matching apple-diag-* bundled doc
+-- Framework API details? --> sosumi.ai/documentation/[framework]
+-- WWDC session content? --> Navigate to developer.apple.com/videos transcript
+-- Xcode MCP setup? --> See setup section above
+-- Build/test via MCP? --> BuildFix/TestFix workflow loops
+-- App Store Connect automation? --> asc-mcp workflows
+-- Bundled guide (Liquid Glass, concurrency, etc.)? --> Read apple-guide-* doc

Anti-Patterns

Using xcodebuild when MCP available

MCP gives IDE state, navigator diagnostics, previews, and resolved packages that CLI does not expose. Use MCP for iterative workflows, CLI for CI/scripted builds.

Parsing build logs instead of navigator issues

XcodeListNavigatorIssues provides structured, deduplicated diagnostics. Build logs contain raw noise.

Skipping tabIdentifier

Most tools fail silently without correct tabIdentifier. Always call XcodeListWindows first.

XcodeWrite for existing files

Use XcodeUpdate (str_replace patches) for editing. XcodeWrite overwrites the entire file.

Loading all 208 asc-mcp tools

Use --workers flag to load only needed workers. Full set wastes context tokens.

Scraping developer.apple.com HTML

Use sosumi.ai for clean markdown. Transcripts are already on WWDC video pages.

Deep Patterns

Xcode MCP Multi-Instance Targeting

pgrep -x Xcode  # Find PIDs
claude mcp add --transport stdio xcode -- env MCP_XCODE_PID=12345 xcrun mcpbridge

Xcode MCP Troubleshooting

SymptomFix
"Connection refused"Launch Xcode, enable MCP in Settings > Intelligence
tools/list emptyOpen a project, approve permission dialog in Xcode
Wrong project targetedUse correct tabIdentifier from XcodeListWindows
Cursor rejects responsesUse XcodeMCPWrapper proxy (schema compliance)
"No such command: mcpbridge"Update to Xcode 26.3+

ASC Release Pipeline

apps_search(query) -> builds_list(appId) -> app_versions_create(appId, versionString)
-> app_versions_attach_build(versionId, buildId) -> app_versions_set_review_details(...)
-> app_versions_submit_for_review(versionId) -> app_versions_create_phased_release(...)

ASC TestFlight Distribution

builds_list(appId) -> builds_set_beta_localization(buildId, whatsNew)
-> beta_groups_create/list -> beta_groups_add_builds(groupId, [buildId])
-> builds_send_beta_notification(buildId)

Bundled Apple Guides (read via MCP axiom_read_skill)

UI: apple-guide-swiftui-implementing-liquid-glass-design, apple-guide-swiftui-new-toolbar-features, apple-guide-swiftui-styled-text-editing, apple-guide-swiftui-webkit-integration

Concurrency: apple-guide-swift-concurrency-updates, apple-guide-swift-inlinearray-span

AI: apple-guide-foundationmodels-using-on-device-llm-in-your-app

Integration: apple-guide-appintents-updates, apple-guide-storekit-updates

Data: apple-guide-swiftdata-class-inheritance

Swift Compiler Diagnostics (bundled)

Concurrency: apple-diag-actor-isolated-call, apple-diag-conformance-isolation, apple-diag-sendable-closure-captures, apple-diag-sending-risks-data-race, apple-diag-mutable-global-variable, apple-diag-nonisolated-nonsending-by-default

Type System: apple-diag-existential-any, apple-diag-protocol-type-non-conformance, apple-diag-opaque-type-inference

Build: apple-diag-deprecated-declaration, apple-diag-strict-language-features, apple-diag-member-import-visibility

Diagnostics

Xcode MCP Not Responding

  1. Check Xcode is running with project open
  2. Verify MCP toggle: Settings > Intelligence > Enable MCP
  3. Check permission dialog appeared and was approved
  4. Re-run XcodeListWindows to verify connection
  5. If Cursor/strict client: use XcodeMCPWrapper proxy

ASC Build Not Found

  • Build processing takes 15-30 minutes after upload
  • Poll builds_get_processing_state -- must return VALID
  • Verify correct app with apps_search bundleId check

Related

  • ax-build -- xcodebuild CLI, build errors, code signing
  • ax-shipping -- App Store submission workflow, review guidelines
  • ax-testing -- Test plans, XCUITest, Swift Testing
  • WWDC transcripts at developer.apple.com/videos
  • sosumi.ai for clean API documentation

Source

git clone https://github.com/Kasempiternal/axiom-v2/blob/main/axiom-plugin/skills/ax-apple-docs/SKILL.mdView on GitHub

Overview

ax-apple-docs consolidates Apple documentation research with MCP tooling: Xcode MCP setup and reference, App Store Connect MCP workflows, WWDC transcript extraction, and sosumi.ai docs. It helps developers access API details, structured diagnostics, and bundled compiler insights in one workflow.

How This Skill Works

The skill provides concrete steps and tooling patterns, including enabling Model Context Protocol in Xcode, adding MCP servers with xcrun mcpbridge, and configuring MCP clients (Claude or Codex). It exposes the Xcode MCP Tools (Discovery, File Ops, Build/Test, Diagnostics) and workflows like BuildFix Loop and TestFix Loop to iteratively fix issues, plus sources for WWDC transcripts and sosumi.ai docs.

When to Use It

  • Setting up Xcode MCP for a new project and enabling MCP tools
  • Diagnosing and fixing build or navigator issues with structured diagnostics
  • Researching Apple framework APIs using sosumi.ai docs
  • Automating App Store Connect tasks with asc-mcp presets
  • Extracting WWDC transcripts to map API names and code descriptions

Quick Start

  1. Step 1: Enable Model Context Protocol in Xcode and add MCP servers (xcode) to your MCP client
  2. Step 2: Run through BuildFix or TestFix loops using XcodeListWindows, XcodeListNavigatorIssues, and XcodeUpdate
  3. Step 3: Reference WWDC transcripts or sosumi.ai docs for API names and detailed references

Best Practices

  • Enable Xcode's Model Context Protocol and the MCP Tools setting before work
  • Add MCP servers for xcode (and others) and verify with XcodeListWindows
  • Use XcodeListNavigatorIssues for structured diagnostics, not raw logs
  • Follow the BuildFix Loop or TestFix Loop for iterative fixes (max 5 iterations)
  • Leverage asc-mcp worker presets for apps, builds, and versions when automating App Store Connect tasks

Example Use Cases

  • Configure MCP in Xcode and verify with XcodeListWindows, then fix a compile issue via XcodeUpdate after XcodeListNavigatorIssues
  • Use XcodeListNavigatorIssues to surface structured diagnostics and patch with XcodeUpdate
  • Research SwiftUI API references via sosumi.ai and document key API names for quick lookup
  • Automate app metadata workflows using asc-mcp with workers apps, builds, versions, and reviews
  • Extract a WWDC transcript for a recent year and pull API names and descriptions for reference

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers