Guide
Generate App Store screenshots from Claude Code
AppSnaps is also an MCP server. Connect it once, and your coding agent — Claude Code, Cursor, or Codex — can read your app, upload your raw screens, and drop a finished, store-ready screenshot set straight into your repo.
Last updated: June 11, 2026
1. Add the server
For Claude Code, one command:
claude mcp add --transport http -s user appsnaps https://appsnaps.io/mcpThe first call opens your browser to sign in with your AppSnaps account — no API key to copy. Cursor connects the same way through its MCP settings; Codex uses a personal access token from your dashboard. Full per-client instructions live in Settings → Connectonce you’re signed in.
2. Ask for screenshots
Inside your app’s repo, prompt your agent:
generate the App Store screenshots for this app using appsnapsThe agent then does the whole flow itself:
- Reads your repo to infer the app’s name and what it does.
- Collects 1–4 raw screenshots — files you point it at, or a folder it asks you to drop them into.
- Uploads them and starts a generation (this is the step that spends a credit — your agent confirms first).
- Downloads the finished 5-slide set into
./app-store/iphone/and saves it to your dashboard.
What you get
The same output as the web app: a cohesive 5-slide set rendered from your real screens — headline, device frame, and background baked in — at App Store dimensions, in one of 11 styles (or AI’s choice). Standard sets cost 1 credit, HD 2 credits, and the iPad add-on 1 more. Credits come from one-shots (from $2.99) or a subscription.
Why agents are good at this
Store screenshots are repo-adjacent work: the copy comes from what the app does, the colors come from the UI, and the output belongs in your release workflow. An agent that already knows your codebase can brief the generator better than a blank form can — and the result lands as files in your project, ready for App Store Connect.