asc-submission

ASC Submission

Prepare apps for App Store review or TestFlight distribution using the App Store Connect MCP server.

Workflows

Workflow A: Full Submission Readiness Check

When the user asks to prepare or check submission readiness, run steps 1–2 sequentially then dispatch parallel validation.

1. Get app ID: Call asc_list_apps and find the app by name/bundle ID.

2. Check version exists: Call asc_list_versions to find a version in PREPARE_FOR_SUBMISSION state. If none exists, create one with asc_create_version.

3. Parallel validation — dispatch two agents simultaneously:

Coordinator (you)
├─► Agent A — Signing + Readiness check   [Fast tier: claude-haiku-4-5 / gpt-4.1-mini / gemini-3.0-flash / kimi-for-coding]
└─► Agent B — Local entitlements scan     [Fast tier: claude-haiku-4-5 / gpt-4.1-mini / gemini-3.0-flash / kimi-for-coding]
         │
         ▼ (both complete)
Coordinator — aggregate results, report missing items, offer to fix

Agent A prompt:

Check submission readiness for app ID: <app_id>

1. Call asc_check_signing with bundle IDs: <list>
   and expected capabilities from the entitlements scan (provided by Agent B)
2. Call asc_check_submission with app ID: <app_id>

Report:
- SIGNING: OK / ISSUES (list mismatches)
- METADATA: OK / MISSING (list required fields)
- SCREENSHOTS: OK / MISSING (list devices/locales)
- OVERALL: READY / BLOCKED (list blockers)

Agent B prompt:

Read local entitlements files and report capabilities for each bundle ID.

1. Find all .entitlements files: find <app-dir> -name "*.entitlements"
2. For each file, extract: app group identifiers, capability keys, bundle ID
3. Return a map: { bundleId: [capability1, capability2, ...] }

This output feeds Agent A's signing check.

1. Report missing items and offer to fix them.

Workflow B: Update Metadata

When the user asks to update metadata, what's new, or description:

1. Get app and version: asc_list_apps then asc_list_versions (find PREPARE_FOR_SUBMISSION version).