ios-ship-doctor
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ios-ship-doctor run preflight on /Users/me/MyApp"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🩺 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.xcprivacyA permission used with no
NS…UsageDescriptionstring (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.
Related MCP server: App Store Connect MCP Server
Quickstart
No install needed — npx fetches and runs it:
npx -y ios-ship-doctor-mcp preflight /path/to/your/appThen 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 onegit 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` commandSupported out of the box: claude, gemini, codex, cursor, vscode, windsurf, zed, generic.
Client | Config file | Root key |
Claude Code |
|
|
Gemini CLI |
|
|
OpenAI Codex CLI |
|
|
Cursor |
|
|
VS Code (Copilot) |
|
|
Windsurf |
|
|
Zed | Zed |
|
Anything else | — |
|
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-appready 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 foundTools
Preflight — local, no credentials
Tool | What it catches |
| Runs every check below → single READY / NOT READY verdict |
| Required-reason APIs used but undeclared, invalid reason codes, missing manifest |
| Camera / location / photos / mic / tracking used with no |
| Apple-listed SDKs shipping without a |
| Placeholder / public test credentials in |
| Missing Privacy Policy / Terms of Use (EULA) links on a paywall + in the App Store description (3.1.2) |
| No demo account for App Review (2.1), missing in-app account deletion (5.1.1(v)), social login without Sign in with Apple (4.8) |
| Stripe/PayPal/Paddle for digital content with no StoreKit (3.1.1) |
|
|
| Lorem ipsum, Stripe test keys, |
| Writes a valid |
| Applies the safe fixes automatically; reports the rest as manual follow-up |
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
Tool | What it does |
| Lists your apps (id, name, bundle id) |
| Pulls recent rejections, maps Review Guideline numbers → summaries + fixes |
| The metadata half of preflight: demo credentials actually filled in, review notes, required screenshot sets |
| Explains any Review Guideline number (offline, no key needed) |
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-readableCopy 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(nojsonwebtokendependency), in the JOSE (IEEE-P1363) format Apple requires.Safe by default — everything is read-only except
generate_privacy_manifestwithwrite=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
Available Tools
6 toolsasc_check_submissionA
Check the App Store Connect side of readiness for the next version: whether demo credentials are actually filled in for a login-gated app (Guideline 2.1 — the most common avoidable rejection), whether App Review notes exist, and whether the required iPhone screenshot sets have anything in them. Complements the local preflight, which can only see the binary.
Inputs: appId (required).
asc_list_appsA
List the apps on your App Store Connect account (id, name, bundle id). Requires ASC_KEY_ID, ASC_ISSUER_ID, and ASC_PRIVATE_KEY(_PATH) env vars. Use the returned app id with asc_get_rejections.
Inputs: no named parameters.
check_placeholder_contentA
Scan source and Info.plist for content that should never reach review: lorem ipsum, Stripe test keys, YOUR_API_KEY-style template tokens, example.com dead links, and template app names still set as CFBundleDisplayName (Guideline 2.1).
Inputs: projectPath (required).
explain_guidelineA
Explain an App Store Review Guideline number (e.g. '5.1.1') in plain language with a typical fix. Works offline — no credentials needed.
Inputs: guideline (required).
generate_privacy_manifestA
Generate a valid PrivacyInfo.xcprivacy covering every required-reason API detected in first-party code (plus anything already declared). By default only PREVIEWS the XML; pass write=true to save it to the app target directory. After writing, the file still must be added to the app target in Xcode.
Inputs: projectPath (required), write.
preflightA
Run ALL App Store readiness checks on an iOS project and return a single prioritized report: privacy manifest vs required-reason API usage, Info.plist usage-description keys, third-party SDK privacy manifests, and placeholder/test-credential traps. Start here — it answers 'is this app ready to submit?'.
Inputs: projectPath (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool serves a distinct, non-overlapping purpose: ASC readiness, app listing, placeholder scanning, guideline explanation, privacy manifest generation, and a comprehensive preflight. No two tools could be confused.
Most tools follow a verb_noun pattern (e.g., check_placeholder_content, generate_privacy_manifest) with a consistent snake_case style. The only outlier is 'preflight' which is a single word, but it is a common term and the overall pattern is clear.
With exactly 6 tools, the server covers the core aspects of iOS app submission readiness without being excessive or lacking. Each tool justifies its presence.
The server covers the full lifecycle of pre-submission checks: placeholder content, privacy manifest generation, Info.plist keys, third-party SDK manifests, ASC credentials and metadata, and a comprehensive preflight that ties it all together. There are no obvious gaps for its stated purpose.
Related MCP Connectors
Finds what Apple and Google would reject in your mobile app before you submit, with the fix.
1App Store Connect operator for AI agents: icons, TestFlight builds, listings, IAP, rejection fixes.
Ship a new iOS app from chat. AI runs App Store Connect, builds, release, and submission through Ap…
Signing, TestFlight, App Store metadata, screenshots and App Review for AI agents, on a NoMac Mac.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to access TestFlight beta tester feedback, including screenshots, crash logs, and text comments from App Store Connect. It works across any platform without requiring Xcode, using official API keys and optional browser automation for full text feedback.8MIT
- AlicenseNot gradedqualityBmaintenanceAutomate App Store Connect from your AI agent. Manage versions, metadata, builds, and submissions through natural language.15 npm8MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Apple App Store Connect resources like apps, builds, TestFlight, and reviews through natural language.20MIT
- AlicenseAqualityCmaintenanceProvides AI assistants direct access to Apple's App Store Connect API, enabling them to manage apps, provisioning data, TestFlight builds, and App Store versions, including creating versions, attaching builds, and submitting for review.14MIT