Claude · App Store Connect

Make and upload App Store screenshots from Claude

Point Claude at your raw simulator captures. MetaRun's Screenshot Studio lays them out in device frames with captions, translates the captions, renders every slide on the server, and uploads them to App Store Connect once you approve.

Setup checked October 2026 against Claude custom connectors

01 · Uplink

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/mcp

02 · 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.

02 · Briefing

What Claude handles here

Screenshots are the part of a release people dread: frame every capture, write captions that fit, redo it all per language, export at Apple's sizes, then upload ten images per display size per language by hand.

MetaRun's studio is fully tool-driven, so Claude can build a project, apply a template, set captions, translate them, render previews you can look at, and then upload. Uploads go through the same preview gate as every other write.

03 · Preflight

Before you start

  • Raw captures of your app: simulator screenshots, UI test output or exported images.
  • An editable version to upload to.
  • For iPhone Duo, app previews or creative assets: the App Asset Library tools.
04 · Execution

How it runs

  1. 01

    Start from your captures

    Local files get an https URL with npx metarun upload, or the studio's own upload tools. Claude creates a project and assigns one capture per slide.

  2. 02

    Design and caption

    The agent applies a template and writes captions. Every slide can be rendered on the server and returned as an image, so you see the real result in the conversation.

  3. 03

    Translate

    Captions are translated per language, and the lint flags text that overflows its frame in a longer language.

  4. 04

    Upload behind a preview

    Each upload previews the target set, size and position. The confirm token is bound to the image bytes, so what you approved is exactly what reaches Apple.

05 · Session

An example session in Claude

Make a screenshot set for my app with five slides about the main features.

  1. studio_create_projectProject created with six slides, one capture each.
  2. Claude asks before running studio_apply_template. You read the preview above and approve.
  3. studio_apply_templateKeynote template applied: background, device frame, caption type.
  4. studio_render_slideSlide 1 rendered at 1320 x 2868 and shown in the conversation.
  5. apple_preview_upload_screenshotPreview: slide 1 to the iPhone 6.9-inch set, English (U.S.), position 1.
  6. Claude asks before running apple_apply_upload_screenshot. You read the preview above and approve.
  7. apple_apply_upload_screenshotUploaded. Apple is processing the image.

Illustrative: your apps, versions and numbers will differ. The tool names and their order are real.

06 · Tools

The MetaRun tools Claude calls

ToolWhat it does
studio_create_projectMetaRunA new screenshot project for the app.
studio_apply_templateMetaRunOne of eight complete designs: background, device placement, caption type.
studio_set_slide_textMetaRunCaptions per slide and per language.
studio_translate_slidesMetaRunTranslate every caption into the project's languages.
studio_render_slideMetaRunRender a slide on the server so you can see it before anything uploads.
studio_lint_assetsreadCheck captions against Apple's asset rules.
apple_preview_upload_screenshotpreview + applyUpload one rendered image to a screenshot set. The token is bound to the image's MD5.
apple_preview_reorder_screenshotspreview + applySet the order shoppers see.
apple_preview_upload_library_assetpreview + applyUpload to Apple's App Asset Library (API 4.5.1), needed for app previews and iPhone Duo.

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.

07 · Apple rules

What Apple enforces, and how MetaRun handles it

Ten screenshots per display size per language

Apple caps each set at ten. The first three are what most shoppers see in search results, which is why order is its own tool.

Uploads come from https URLs

MetaRun fetches the image from an https URL behind an SSRF guard, checks its size and type from the bytes, and binds the confirm token to the file's MD5.

iPhone Duo needs the App Asset Library

Apple's older screenshot sets have no iPhone Duo display type, and Apple requires Duo screenshots on submissions from April 2027. Duo, app preview videos and creative assets go through the library tools.

Server renders skip the 3D frame

Slides rendered on the server use the 2D device frame. 3D mockups render in the studio in your browser; the tool says so in its notes when it falls back.

08 · Comms

What to ask Claude

  • Ask Claude: Make a screenshot set for my app with five slides about the main features.
  • Ask Claude: Show me how slide 1 looks in the App Store.
  • Ask Claude: Translate the captions into Spanish and upload both languages.
09 · Safety

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.

Apple key stays on MetaRun, encryptedPreview before every writeRecorded, revertible from history
10 · FAQ

Frequently asked questions

Can Claude upload screenshots from my machine?

Yes, via an https URL. npx metarun upload <file> returns one for a local PNG or JPEG, and the studio tools take uploads directly. The upload itself runs on MetaRun's servers with your Apple key, which never touches your machine.

Do I have to use MetaRun's studio?

No. If you already have final images, Claude can upload and order them directly with the screenshot tools. The studio is for when you want framing, captions and translations done too.

What sizes does it support?

Every display size Apple lists for screenshot sets, plus the App Asset Library's catalog for newer placements such as iPhone Duo. apple_get_asset_catalog returns Apple's current specs.

Can I see the screenshots before they go up?

Yes. studio_render_slide returns each slide as an image and studio_store_preview shows them in App Store context. Nothing uploads until you approve the apply.

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 "screenshots" 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

In depth: Screenshot studio

Agent access

14-day free trial with agent access. No credit card. Your Apple key stays encrypted on MetaRun.