🩺 iOS Ship Doctor

Catch App Store rejections before you hit Submit.

An MCP server that lets your AI assistant — Claude Code, Gemini CLI, Codex, Cursor, Copilot, Windsurf, Zed — diagnose why your iOS app will be rejected — privacy manifests, missing permission strings, unlisted SDKs, leftover test credentials — and then fix them. When Apple does reject you, it pulls the rejection and maps it to a plain-English fix.

Why

Apple's review pipeline silently rejects builds for things you can't see in Xcode:

• A required-reason API used in code but not declared in PrivacyInfo.xcprivacy

• A permission used with no NS…UsageDescription string (instant crash + reject)

• A third-party SDK on Apple's list shipping without its own privacy manifest

• A placeholder test credential (like Google's sample AdMob ID) left in Info.plist

Each one costs you a submission cycle — hours or days of round-trips. Ship Doctor checks all of them in seconds and tells you exactly what to change.

Existing App Store MCPs are thin API wrappers that submit your app. Ship Doctor is the one that tells you why it won't pass first.

Quickstart

No install needed — npx fetches and runs it:

npx -y ios-ship-doctor-mcp preflight /path/to/your/app

Then wire it into whichever assistant you use. This is a standard stdio MCP server — it is not Claude-specific and works with any MCP client. Let it print the exact config for yours:

npx -y ios-ship-doctor-mcp config              # every client
npx -y ios-ship-doctor-mcp config gemini       # just one

git clone https://github.com/menansali/ios-ship-doctor.git
cd ios-ship-doctor
npm install && npm run build
npm link           # exposes the `ios-ship-doctor-mcp` command

Supported out of the box: claude, gemini, codex, cursor, vscode, windsurf, zed, generic.

The two footguns the generator handles for you: Codex silently ignores mcp-servers (it must be mcp_servers), and the printed node path avoids version-pinned Homebrew/nvm paths that break on the next upgrade.

Then just ask:

Is /path/to/my-app ready to submit to the App Store?

Example

🩺 Ship Doctor preflight — /Users/you/Desktop/MyApp

VERDICT: NOT READY — 1 issue that commonly causes rejection.
(1 error, 1 warning, 6 passed)

❌ [credential-traps] Google AdMob TEST application ID in Info.plist
   Found placeholder/test value "ca-app-pub-3940256099942544".
   ↳ MyApp/Info.plist
   💡 Replace GADApplicationIdentifier with your real ca-app-pub-… ID.

⚠️ [export-compliance] Missing ITSAppUsesNonExemptEncryption in Info.plist
   Without this key, App Store Connect prompts about encryption on every submission.
   💡 Add <key>ITSAppUsesNonExemptEncryption</key><false/> if you only use HTTPS/TLS.

✅ [privacy-manifest] Privacy manifest consistent with API usage
✅ [usage-descriptions] All permission strings present
✅ [dependencies] SDK privacy manifests OK
✅ [app-icon] App icon asset found

Tools

Preflight — local, no credentials

preflight also checks export compliance, App Transport Security, app-icon presence, banned APIs (UIWebView), launch screen, version/build sanity, and deployment target. Dependency scanning covers both CocoaPods and Swift Package Manager.

Project layouts understood: classic Info.plist projects, modern projects with GENERATE_INFOPLIST_FILE and no plist file (keys read from INFOPLIST_KEY_* build settings), ios/ subdirectories, and monorepos where the .xcodeproj sits a level or two down.

What this does not check

Ship Doctor reads project files. It cannot see the things most rejections are actually about:

• Crashes and incomplete features (2.1) — the most common rejection; needs the app running

• Design quality (4.0) and spam/duplicate (4.3) — human judgement

• Metadata accuracy (2.3) — whether screenshots match the real app

• Privacy label accuracy (5.1.1) — whether declared data collection matches SDK behaviour

• Anything a dependency does; source scanning is first-party only

A clean run means "no automated check fired", not "this will be approved."

Rejection recovery — needs an App Store Connect API key

Create a key at App Store Connect → Users and Access → Integrations → App Store Connect API, download the .p8, and add env vars to the MCP config:

{
  "mcpServers": {
    "ios-ship-doctor": {
      "command": "ios-ship-doctor-mcp",
      "env": {
        "ASC_KEY_ID": "XXXXXXXXXX",
        "ASC_ISSUER_ID": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
        "ASC_PRIVATE_KEY_PATH": "/absolute/path/to/AuthKey_XXXXXXXXXX.p8"
      }
    }
  }
}

The .p8 never enters the repo — it stays on your machine and is read at runtime.

Manual configuration

If you'd rather not use npm link, point your client at the built file directly (this shape works for Claude Code, Gemini CLI, Cursor, Windsurf and most others):

{
  "mcpServers": {
    "ios-ship-doctor": {
      "command": "node",
      "args": ["/absolute/path/to/ios-ship-doctor/dist/index.js"]
    }
  }
}

projectPath in any tool can be your repo root (with an ios/ folder) or the ios/ directory itself.

Use it in CI (no assistant required)

The same binary runs as a one-shot command that exits non-zero on blocking issues:

npx -y ios-ship-doctor-mcp preflight /path/to/app          # human-readable
npx -y ios-ship-doctor-mcp preflight /path/to/app --json   # machine-readable

Copy examples/preflight-gate.yml into your app repo's .github/workflows/ to block PRs that would fail App Store review.

How it works

• Required-reason APIs — scans first-party source for Apple's documented API signatures, then diffs against your declared PrivacyInfo.xcprivacy.

• App Store Connect auth — an ES256 JWT signed with Node's built-in crypto (no jsonwebtoken dependency), in the JOSE (IEEE-P1363) format Apple requires.

• Safe by default — everything is read-only except generate_privacy_manifest with write=true.

Roadmap

• Auto-fix tools (patch Info.plist, generate privacy manifest)

• More preflight checks: launch screen, version sanity, deployment target

• SwiftPM dependency scanning

• CLI + CI mode

• Entitlements sanity (push, app groups, associated domains)

• Privacy nutrition-label cross-check against SDK data collection

• Draft reviewer replies from a rejection

Contributing

Issues and PRs welcome. Adding a check usually means one entry in src/knowledge.ts plus a small function in src/scanner.ts.

License

MIT © menansali