Comparison
| Server | Runs | Sign-in | Designs the set | Agent uploads to ASC | Price |
|---|---|---|---|---|---|
| Agent C | Hosted (Streamable HTTP) | API key | Yes — Claude designs the whole set | Yes — send_to_app_store | Free to design · $9.99/set or Studio |
| Screenies | Hosted (HTTP) | OAuth sign-in | Yes — headlines and scenes | No (dashboard only) | $9–$39 credit packs |
| AppLaunchFlow | Hosted (HTTP) | Browser sign-in | Yes — layouts and copy | Not documented for MCP (dashboard upload) | Unlimited plan, €15/mo |
| ButterKit | Local bridge (Mac app must be open) | None (local) | No — you design, AI translates | Yes — App Store Connect tools | $99 one-time Pro |
| AppScreenshotStudio | Local (npx) | API key | Yes — chat-driven | No | Upper plans, billed yearly |
| storeshots-mcp and similar open-source servers | Local | None | Renders frames; your agent writes the copy | No | Free |
| app-publish-mcp, appstore-connect-mcp | Local | Your ASC key | No — publishing only | Yes | Free |
What a full run looks like
This is a real run with Agent C connected to Codex. The whole request was one sentence:
> make App Store screenshots for Tiny Legacy from ./shots
● agent-c · get_upload_link ✓
● curl → 6 screenshots uploaded ✓
● agent-c · design_set ✓ (previews returned to the agent)
● agent-c · edit_set slide 2 → "Gentle memory prompts for big feelings" ✓The agent looked at the previews, decided slide 2's headline could be warmer, and changed it. With the set unlocked, one more call, send_to_app_store, puts the screenshots into the app's draft version. Nothing is submitted for review.
Hosted or local?
Hosted servers (Agent C, Screenies, AppLaunchFlow) work from any machine and any MCP client, with nothing to install. Local servers (ButterKit, AppScreenshotStudio, the open-source renderers) run on your computer: good for privacy and offline use, but ButterKit needs its Mac app open with a document loaded, and npx servers need Node.
Getting big screenshots to the server
Raw screenshots are several megabytes each, far too big to pass through the conversation. Agent C hands the agent a one-time upload link (get_upload_link) that it can curl files to, so images never go through the model and the agent never sees your API key. Screenies uses a similar upload-request tool.
Set up Agent C in a minute
Create a key in Agent C → Settings, then in Claude Code:
claude mcp add --transport http agent-c https://api.theagentc.io/mcp \
--header "Authorization: Bearer YOUR_AGENT_C_KEY"Cursor, Codex and Claude Desktop setup is on the MCP page. The server is also listed in the official MCP Registry as io.theagentc/app-store-screenshots, and the description lives on GitHub.
FAQ
Can Claude Code make App Store screenshots?
Yes, through an MCP server. With Agent C connected, you can ask Claude Code to make App Store screenshots from a folder of raw screenshots; it uploads them, Claude designs the set, and after you approve it can send the set straight to your App Store Connect draft.
Which App Store screenshot MCP server can upload to App Store Connect?
Agent C (hosted, send_to_app_store tool) and ButterKit (local Mac app with App Store Connect tools) both upload from the agent. Publishing-only servers like app-publish-mcp also upload but do not design screenshots.
Is it safe to let an agent upload screenshots?
With Agent C, the agent can never pay or submit for review: unlocking returns a checkout link for you, and screenshots only land in an editable draft version that you review and submit yourself.