Write What's New in every language with Claude
Claude already knows what changed in this release. Ask it to turn that into What's New, translate it, and stage it for every language on your listing. MetaRun holds each one to Apple's limits and shows the before and after per language.
Setup checked October 2026 against Claude custom connectors
Connect Claude once
01 · Add a custom connector
In Claude, open Customize, then Connectors, and choose Add custom connector. Name it MetaRun and paste the server URL:
https://metarun.dev/api/mcp02 · Connect
Click Connect. Claude opens MetaRun in your browser to sign in; pick read-only or read and change.
03 · Team and Enterprise
An Owner adds the connector once under Organization settings, Connectors. Each member then clicks Connect and signs in to their own MetaRun account.
What Claude handles here
Release notes are the last thing anyone writes. By then the version is ready, the build is processed, and twelve languages still say last month's text. Copying translations into App Store Connect one locale at a time takes longer than writing them.
Through MetaRun, Claude writes and translates, and MetaRun does the parts that must be exact: it reads the live version, checks What's New against Apple's 4,000-character limit, stages one change per language, and reports which languages are still missing it.
Before you start
- An update, not a first release: What's New only exists after the app has shipped once.
- The version still editable (being prepared, ready for review, or rejected).
- Something to work from: a changelog, the commit log, or your own notes.
How it runs
- 01
Gather what changed
Claude works from what it can see: your changelog, merged pull requests, the commit log since the last tag, or what you tell it.
- 02
Read the version in every language
MetaRun returns the version's localizations so the agent knows which languages exist and what they say now.
- 03
Stage one change per language
Each language gets its own preview with the old and new text. Anything over 4,000 characters is refused at preview, not by Apple after submission.
- 04
Confirm coverage
Before calling the job done, Claude reads listing coverage, which lists any language still missing What's New.
An example session in Claude
Here's what changed in 2.4: offline sync, a new widget, faster launch. Write What's New and stage it in every language.
- apple_list_version_localizationsVersion 2.4 has 12 languages. What's New is empty in each.
- apple_preview_set_version_localizationPreview: English (U.S.) What's New, 412 of 4,000 characters.
- Claude asks before running apple_apply_set_version_localization. You read the preview above and approve.
- apple_apply_set_version_localizationApplied for English (U.S.).
- apple_get_listing_coverage11 languages still missing What's New. Claude continues with those.
Illustrative: your apps, versions and numbers will differ. The tool names and their order are real.
The MetaRun tools Claude calls
| Tool | What it does |
|---|---|
| apple_list_version_localizationsread | Every language on the version with its current What's New, description and keywords. |
| apple_preview_set_version_localizationpreview + apply | Stage What's New (or description, keywords, URLs) for one language. |
| apple_get_listing_coverageread | Which languages are still missing which fields, so the job isn't declared done early. |
| apple_get_listing_editabilityread | Whether the version's text is editable right now. |
| aso_lint_metadataread | Checks copy against App Store rules before it's staged. |
| apple_preview_set_promotional_textpreview + apply | The 170-character line above the description that changes live, without review. |
| aso_schedule_promo_textMetaRun | Schedule promotional text to switch at a set time, for example on launch day. |
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
No What's New on a first version
Apple has no What's New field until the app has shipped once. The API rejects it and App Store Connect hides it, so MetaRun only asks for it on updates.
4,000 characters per language
What's New and the description each allow 4,000 characters. Promotional text allows 170 and is the only one of the three that changes without review.
Text locks once the version is in review
What's New is editable while the version is being prepared or after a rejection. apple_get_listing_editability tells the agent which fields are locked and why, instead of a write failing.
Adding a language creates rows Apple fills in
When a new language is added, Apple creates that language's other localization rows on its own. MetaRun's confirm token is keyed on the language, not Apple's row id, so your approved change doesn't fail as drift.
What to ask Claude
- Ask Claude: Here's what changed in 2.4: offline sync, a new widget, faster launch. Write What's New and stage it in every language.
- Ask Claude: Make the French release notes shorter.
- Ask Claude: Is What's New filled in for every language?
How Claude asks before a change
Claude asks before it calls a connector's tool unless you've set that tool to always allow. Keep MetaRun's apply tools on ask: that's the moment you see the change and decide, and it needs the confirm token from a fresh preview either way.
Frequently asked questions
Who writes the translations, Claude or MetaRun?
Claude does. MetaRun reads the live listing, checks the limits, and stages one change per language for you to approve. Translations through your own agent don't use MetaRun's AI translation budget.
Can Claude update release notes after the app is live?
Not What's New: it locks with the version. Promotional text is the exception and changes the live listing immediately, so that's what to use for a post-launch message.
How many languages can it handle at once?
Every language on your listing. Each one is its own preview, so you can approve some and skip others.
Will it overwrite my description by accident?
Only fields the agent names are touched, and each preview shows the field's old and new text before anything is applied.
How do I connect Claude to App Store Connect?
In Claude, open Customize, Connectors, Add custom connector, paste https://metarun.dev/api/mcp and click Connect to sign in to MetaRun. After that, ask for "release notes" in plain words and Claude picks the MetaRun tools.
Does Claude 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 holds a MetaRun token that you can revoke in Settings at any time.
More with Claude
Claude
Localize your listing
Name, subtitle, keywords and description in every App Store language, limits checked.
OpenClaude
Submit for review
Attach the build, clear export compliance, run the readiness sweep, submit.
OpenClaude
ASO keywords
Find keywords from App Store autocomplete, track ranks, and lint your metadata.
OpenClaude
Phased release
Choose how an approved version goes out, then pause, resume or finish a phased rollout.
OpenRelease notes with another agent
In depth: Listing translation
Agent access
14-day free trial with agent access. No credit card. Your Apple key stays encrypted on MetaRun.