Submit your app for App Review from Claude Code
Your build finished processing. Ask Claude Code to ship it: MetaRun attaches the build to the version, checks every field App Review will look at, and shows the submission before anything is sent. Resubmitting after a rejection goes through the same submission, the way App Store Connect does it.
Setup checked October 2026 against Claude Code MCP docs, permissions
Connect Claude Code once
01 · Add the server
Run it in any terminal. --scope user makes MetaRun available in every project; leave it out to limit it to the current one.
claude mcp add --transport http --scope user metarun https://metarun.dev/api/mcp02 · Sign in
In a Claude Code session, run /mcp, choose metarun and authenticate. MetaRun opens in your browser, where you pick read-only or read and change. From a plain shell, claude mcp login metarun does the same.
/mcp03 · Optional: add the skills too
The MetaRun plug-in bundles the same server with six mission skills (release handoff, worldwide pricing, localization, review inbox, ASO audit, store media).
claude plugin marketplace add metarun/metarun-skills
claude plugin install metarun-skills@metarunPrefer a personal access token (scripts, CI)?
Add the server with a token
Mint a personal access token in MetaRun under Settings, MCP. It's shown once and can be revoked any time.
claude mcp add --transport http --scope user metarun https://metarun.dev/api/mcp \
--header "Authorization: Bearer $METARUN_TOKEN"Or share it with your team in .mcp.json
Project scope writes .mcp.json at the repo root. Claude Code expands ${METARUN_TOKEN} from each person's environment, so the token itself is never committed.
{
"mcpServers": {
"metarun": {
"type": "http",
"url": "https://metarun.dev/api/mcp",
"headers": { "Authorization": "Bearer ${METARUN_TOKEN}" }
}
}
}What Claude Code handles here
Submitting by hand is six screens in App Store Connect: pick the build, answer the encryption question, fill in review contact and demo account details, check that every language has its screenshots and description, press Add for Review, then Submit. Miss one field and the button stays grey with no reason given.
Through MetaRun the agent does the same steps as tool calls. The readiness sweep reads the version, the build, the listing in every language and the review details, and returns one list of blockers before any write. Fix those, preview the submission, approve it, and it is in Apple's queue.
Before you start
- A version in Prepare for Submission. If there isn't one, apple_preview_create_version makes it.
- A processed build for that version, uploaded from Xcode, Xcode Cloud, fastlane or your CI.
- An App Store Connect API key in MetaRun with the Admin or App Manager role.
How it runs
- 01
Find the version and the build
Claude Code lists the app's versions and builds, picks the processed build that matches the version you named, and previews attaching it. A build still processing is reported as such, not attached.
- 02
Clear what App Review will ask
If the build has no export compliance answer, the agent previews one. If review contact details or the demo account are missing, it previews those too. Each is its own change with its own before and after.
- 03
Run the readiness sweep
The submit preview reads the version, every language's description and screenshots, What's New on an update, the review details and any submission already in flight. Blockers come back as a list with the tool that fixes each one.
- 04
Submit with an explicit acknowledge
The apply takes the preview's confirm token plus acknowledge set to true. If anything changed on Apple's side since the preview, the token no longer matches and nothing is sent.
An example session in Claude Code
The 2.4 build just finished uploading. Attach it to version 2.4 of com.example.app, sort out export compliance, and tell me what still blocks submission.
- apple_list_versionsVersion 2.4 is in Prepare for Submission.
- apple_list_buildsBuild 312 finished processing a few minutes ago.
- apple_preview_set_version_buildPreview: attach build 312 to version 2.4.
- Claude Code asks before running apple_apply_set_version_build. You read the preview above and approve.
- apple_apply_set_version_buildAttached. Recorded in change history.
- apple_preview_submit_for_reviewSweep: no blockers. One note: App Privacy answers are entered in App Store Connect.
- Claude Code asks before running apple_apply_submit_for_review. You read the preview above and approve.
- apple_apply_submit_for_reviewSubmitted with acknowledge set to true. Version 2.4 is Waiting for Review.
Illustrative: your apps, versions and numbers will differ. The tool names and their order are real.
The MetaRun tools Claude Code calls
| Tool | What it does |
|---|---|
| apple_get_listing_editabilityread | Which parts of the listing are locked right now, and why. |
| apple_list_buildsread | Processed builds for the app, newest first, with their processing state. |
| apple_preview_set_version_buildpreview + apply | Attach a processed build to the version. Required before submitting. |
| apple_preview_declare_build_encryptionpreview + apply | Answer export compliance for the build, or reuse an existing declaration. |
| apple_preview_set_review_detailpreview + apply | Contact details, demo account and notes for the App Review team. |
| apple_preview_submit_for_reviewpreview + apply | Runs the readiness sweep and previews the submission. Needs an explicit acknowledge to apply. |
| apple_list_review_submissionsread | Every submission with its state, each item's verdict and who submitted it. |
| apple_preview_cancel_review_submissionpreview + apply | Withdraw a submission from Apple's queue, naming exactly which one. |
Each preview has an apply twin (the same name with apply instead of preview) that only runs with the confirm token from a fresh preview, and refuses if App Store Connect changed in between. MetaRun tools save to your MetaRun workspace only (studio projects, tracked keywords), never to Apple.
What Apple enforces, and how MetaRun handles it
One submission at a time per platform
Apple lets one app-version submission wait for or sit in review per platform. The sweep blocks a second instead of letting Apple refuse it halfway through.
A rejection resubmits through its own submission
After a rejection Apple keeps the version inside the rejected submission and refuses to add it to a new one. MetaRun marks the item resolved and resubmits that same submission, which is what the Resubmit button in App Store Connect does. Verified against a live app on 11 September 2026: same submission id, item moved from Rejected to Ready for Review.
App Privacy has no API
Apple's App Store Connect API cannot read or write App Privacy answers. On a first submission the sweep warns about it rather than blocking, and apple_build_privacy_answers turns your PrivacyInfo.xcprivacy files into the exact answers to enter by hand.
App Review's message is not in the API either
The rejection reason, the guideline cited and any attachments only exist in App Store Connect. MetaRun returns a direct link to that page and the agent is told not to guess the reason.
What's New only exists after the first release
A first version has no What's New field and the API rejects one. The sweep only requires it on an update.
What to ask Claude Code
- Ask Claude Code: The 2.4 build just finished uploading. Attach it to version 2.4 of com.example.app, sort out export compliance, and tell me what still blocks submission.
- Ask Claude Code: Use the review notes in docs/review-notes.md for the App Review details, then preview submitting 2.4.
- Ask Claude Code: We got rejected. Show me the submission state and the link to Apple's message, then resubmit once I've replied.
Run it from a script with Claude Code
claude -p runs one request with no interactive session. The browser sign-in can't complete inside -p, so sign in once interactively first, or configure the server with a personal access token in CI. Tools missing from --allowedTools are refused in -p mode.
Read-only check, safe to schedule
claude -p "Check whether version 2.4 of com.example.app is ready to submit for review and list every blocker. Read and preview only; do not apply anything." \
--allowedTools "mcp__metarun__apple_get_listing_editability,mcp__metarun__apple_list_builds,mcp__metarun__apple_preview_set_version_build,mcp__metarun__apple_preview_declare_build_encryption,mcp__metarun__apple_preview_set_review_detail,mcp__metarun__apple_preview_submit_for_review,mcp__metarun__apple_list_review_submissions,mcp__metarun__apple_preview_cancel_review_submission"Only reads and previews are on that list, so nothing can reach App Store Connect unattended. Run applies in an interactive session where Claude Code can ask you.
How Claude Code asks before a change
Claude Code asks before every MCP tool call by default. You can allow a tool for the session or permanently; allow rules look like mcp__metarun__apple_list_versions for one tool, and mcp__metarun__* allows the whole server, applies included. Allowing reads and previews is reasonable. Leave the apply tools on ask: that prompt is the confirm step for every App Store change.
Frequently asked questions
Can Claude Code submit my app for review without asking me?
Not through MetaRun's contract. The submit apply needs a confirm token from a fresh preview plus an explicit acknowledge, and Claude Code asks you before it runs the tool unless you have pre-approved that exact tool. Pre-approve reads and previews if you like; keep applies on ask.
What does the readiness sweep check?
The attached build and its processing state, export compliance, review contact and demo account, every language's description, keywords and screenshots, What's New on an update, and whether another submission is already waiting or in review on the same platform.
Does MetaRun upload the build?
No. Xcode, Xcode Cloud, fastlane or any CI uploads the build to App Store Connect as usual. MetaRun picks up from there: attach, answer compliance, submit.
What happens after a rejection?
Ask Claude Code for the submission state. You get each item's verdict and a link to App Review's message in App Store Connect, since that message has no API. Once you've fixed and replied, the agent resubmits the same submission.
How do I connect Claude Code to App Store Connect?
Run claude mcp add --transport http --scope user metarun https://metarun.dev/api/mcp, then run /mcp in Claude Code and sign in to MetaRun in your browser. After that, ask for "submit for review" in plain words and Claude Code picks the MetaRun tools.
Does Claude Code see my App Store Connect key?
No. Your App Store Connect API key stays envelope-encrypted on MetaRun's servers and is decrypted per request. Claude Code holds a MetaRun token that you can revoke in Settings at any time.
More with Claude Code
Claude Code
Phased release
Choose how an approved version goes out, then pause, resume or finish a phased rollout.
OpenClaude Code
Release notes
Write What's New from your changelog and stage it in every language.
OpenClaude Code
TestFlight
Hand builds to tester groups, write What to Test, and read crash feedback.
OpenClaude Code
App Privacy and compliance
Turn your privacy manifests into App Privacy answers; set age rating and export compliance.
OpenSubmit for review with another agent
In depth: App Store Connect MCP server
Agent access
14-day free trial with agent access. No credit card. Your Apple key stays encrypted on MetaRun.