Apppshot MCP

Your coding agent makes your App Store screenshots

Connect Apppshot to your coding agent and ask for App Store screenshots. Your agent reads your project, studies how similar apps lay out their sets, writes the captions, and renders the panels at 1290×2796 on your computer. No account, no API key, nothing to host.

Install

claude mcp add apppshot -- npx -y apppshot-mcp

Using another agent? Add npx -y apppshot-mcp as an MCP server.

Then, in your app's project:

Make App Store screenshots for my app

What happens

  1. Reads your project

    What the app does, who it's for, its brand colour, and whether its UI is light or dark.

  2. Gets your real screens

    It uses the ones you have, or helps you capture them. It never invents UI.

  3. Studies similar apps

    It looks at shipped sets from apps of the same kind to learn their order, captions and colour, without copying them.

  4. Writes and checks the set

    It writes the captions and config, then validates them against App Store limits and the craft rules.

  5. Renders the PNGs

    It renders every panel with your own browser, looks at them as a row, and tells you what it chose.

Tools

get_guide The workflow and the rules: order, captions, templates.
get_capture_guide How to capture real screens from your app when you have none.
list_kinds Every kind of app in the gallery, with how many sets each has.
get_patterns What sets for your kind of app usually do, measured across the gallery.
find_references Up to five shipped sets of the same kind, with their measured colour and treatment.
get_reference One set's measurements and its panels, for your agent to look at.
check_set Validates the config before anything renders, and flags copy that reads as AI-made.
render_set Renders the panels to PNGs with your local browser.

Screenshots that don't look AI-made

Your agent gets rules for this as soon as it connects, so you don't have to ask. They keep captions plain and specific, and rule out hype words, emoji, unverifiable claims and decorative blobs. check_set flags what slips through.

The rules are adapted from unslop by Damir Sokolovsky, licensed under CC BY 4.0.

What you need

  • Node 20 or newer
  • Chrome, Chromium, Brave or Edge, for rendering
  • Claude Code, Codex, OpenCode or another MCP client

On macOS and Linux your browser is found automatically. On Windows, or for a custom install, set BROWSER_PATH:

claude mcp add apppshot -e BROWSER_PATH=/path/to/chrome -- npx -y apppshot-mcp

Your code stays yours

It runs on your computer. Your code, your screens and the panels it renders stay there. It downloads the gallery's data from apppshot.xyz and reference screenshots from Apple, and sends nothing about your project to anyone. Read the privacy page.

Reference sets belong to the developers who made them. Use them to learn, not to copy. Terms.