Edit your entire App Store listing:every locale, one screen

App Store Connect is a compliance surface, not an editing tool. Metadata lives one locale per screen, bulk operations do not exist, there is no draft state beyond a version, and a mistaken save simply becomes the new truth. Updating What's New in 28 languages is 28 page loads, and renaming a subtitle across locales is an afternoon.

MetaRun treats the listing as one document with 40 views. Edits happen in place across locales, stage into a single reviewable change set, and apply in one confirmed pass. The official API does the writing, so App Store Connect always agrees with what you see.

Because every write flows preview, confirm, apply, there is always a moment where you see exactly what will change before it does: field-level diffs, per-locale. Because every applied change is recorded, there is always a way back: the revert engine rebuilds the previous state and runs it through the same preview pipeline, so undoing is as safe as doing.

The editor also knows Apple's own rules: which fields need a new version (name, subtitle, keywords, description) versus which apply instantly (promotional text), and which surfaces are currently locked by review state. Errors you would have discovered from a rejection email surface as greyed-out fields with reasons instead.

The same editing layer answers the manual workspace, MILO, and the MCP server. "Set the promo text everywhere to announce the sale, and schedule it to revert Monday" is a sentence MILO can execute against the identical staged pipeline your hands would use.

For developers who live in their IDE, the MCP server exposes every metadata operation as tools: your coding agent can update What's New from your changelog as part of the release ritual, with the same confirm gate protecting the store.