开源MCP工具：捕获iOS和macOS应用截图

Prerequisites

1. Create an App Store Connect API key at https://appstoreconnect.apple.com/access/integrations/api. Choose either Admin or App Manager access. Download the AuthKey_XXXXXX.p8 file and keep it safe; Apple only lets you download it once.
2. Record the Key ID (10-character alphanumeric) and Issuer ID (a UUID) from the same page.

Install

Requires macOS 14+ (Sonoma or later) on Apple Silicon (arm64). Intel Macs are not supported.

Confirm the test target builds and the test is discoverable

xcodebuild build-for-testing \ -workspace Example.xcworkspace \ -scheme Example \ -destination 'platform=iOS Simulator,name=iPhone 17 Pro' \ 2>&1 | tee build.log

`storescreens setup`

Interactive wizard that generates a screenshot test file and wires it into your config. It scans your Swift source to auto-discover screens from TabView, NavigationLink, .sheet, .fullScreenCover, and Navigator route patterns.

$ storescreens setup

Project Detection
  ✓ Found project: MyApp.xcodeproj
  ✓ Detected scheme: MyApp

UI Test Target
  ✓ Found UI test target: MyAppUITests

Screenshot Screens
  Found 4 screens in your source code:
    1. Home (TabView)
    2. Search (TabView)
    3. Settings (NavigationLink)
    4. Profile (sheet)

  Press Enter to use these, or type your own (comma-separated)
  >
  ✓ Using discovered screens.

  ✓ Wrote MyAppUITests/ScreenshotTests.swift (4 screenshots)
  ✓ Updated storescreens.yml

If no screens are found in your source, it falls back to asking you to type them manually. If no UI test target exists, it prints step-by-step instructions to create one in Xcode.

Use --non-interactive to skip prompts and use auto-discovered screens (or defaults if none found).

(default), or "verbose" (full xcodebuild output).

builds. When unset, a per-run temp dir is used and cleaned up after.

Install

1. Download DMGs from https://developer.apple.com/design/resources/ (Product Bezels section; iPhone, iPad, MacBook as needed).
2. Double-click each DMG to mount.
3. Run:

storescreens bezels import

This auto-scans /Volumes/ for Apple Design Resource DMGs, classifies PSDs by screen pixel dimensions, applies your colorway preferences, and exports transparent-screen PNGs + JSON sidecars to ~/Library/Application Support/storescreens/bezels/.

Quick Start

```bash cd /path/to/your/xcode-project

custom: https://example.com/my-flag.svg

Quick start

render:
  enabled: true
  output_dir: ./storescreens-framed

  background:
    color: "#1a1a2e"

  caption:
    title:
      font: system
      weight: bold
      font_size_pct: 5.5
      color: "#ffffff"
    min_height_pct: 22

  chrome:
    style: stroke
    stroke_color: "#ffffff"
    stroke_width: 3

  slides:
    "Home":
      caption: "Your recipes, organized."
    "Search":
      caption:
        - Find anything
        - in *seconds*.
    "Detail":
      caption:
        title: Every **detail**, at a glance.
        subtitle: Powered by AI
        highlights:
          - { match: detail, color: "#feb909", weight: heavy }

Run the render independently:

storescreens render

Or run capture with the render pass included (auto-enabled by render.enabled: true):

storescreens capture

Use --no-render to skip the render pass on a given capture run.

2. Generate screenshot UI tests

storescreens setup

4. Capture screenshots on all devices (--verbose for live output)

storescreens capture --verbose ```

`storescreens screenshot`

Takes a quick screenshot of a running simulator's current screen. No build, no tests - just captures whatever is on screen and saves it to a file. Intended for quick visual checks during UI development.

```bash

Screenshot the first booted simulator

storescreens screenshot

Screenshot a specific simulator

storescreens screenshot --simulator "iPhone 17 Pro" --output screenshot.png

gallery order, and the mtime stamp on captured PNGs so `ls -t` / Finder

screenshots whose name appears here are kept.

screenshots:

battery) for clean screenshots. Default: true. Set to false to leave

operator; override when a specific screenshot needs different values.

Advanced: keep older `preview_*.html` pages on the gallery index under

Rendering captioned screenshots

storescreens can post-process captured screenshots into framed, captioned images suitable for App Store Connect uploads. Add a render: block to storescreens.yml and run storescreens render (or let it run automatically after storescreens capture).

1. Generate a config file

storescreens init

Configuration

storescreens.yml:

```yaml project: "MyApp.xcodeproj" scheme: "MyApp"

devices: - simulator: "iPhone 17 Pro Max" - simulator: "iPhone 17 Pro" - simulator: "iPad Pro 13-inch (M5)" # macOS devices run tests natively (no simulator) # - simulator: "Mac 2560x1600" # platform: macOS

Multiple locales (optional) - runs the full capture once per locale

Custom flags for the HTML preview gallery (optional).

Render pass (optional): composites captioned images from captures

App Store search preview (optional): renders a faithful iPhone search

Configure credentials

Either set environment variables (CI-friendly):

export ASC_KEY_ID=ABCDE12345
export ASC_ISSUER_ID=69a6de84-03c8-47e3-e053-5b8c7c11a4d1
export ASC_KEY_PATH=~/.appstoreconnect/AuthKey_ABCDE12345.p8

Or generate a pre-filled credentials template and edit it:

storescreens auth init

This writes ~/.storescreens/asc-credentials.yml (0600 perms) with commented placeholders for key_id, issuer_id, and key_path, and opens it in your editor. Replace the three REPLACE_ME values with your real credentials.

Or run the interactive login that prompts for each value:

storescreens auth login

Either way, verify with:

storescreens auth status

This mints a JWT and hits /v1/users to confirm the key works.

Colorway / model preference

By default the importer picks "Space Black" when available, else Silver / Natural Titanium. Override per project:

render:
  chrome:
    style: bezel
    model_preference: [Pro Max, Pro, Air]
    colorway_preference: ["Cosmic Orange", Silver]

Three pieces, one workflow

StoreScreens ships as three complementary pieces. Most users only need the CLI; the other two exist to make AI coding assistants first-class operators.

Both the CLI and MCP server are installed by brew install storescreens.

How this compares to other Xcode MCP servers

StoreScreens is purpose-built for one job: generating the complete set of App Store Connect screenshots. It is not a general Xcode control surface, and it is not competing with the general-purpose Xcode MCP servers, it complements them.

If you are shipping an app, you will likely use StoreScreens alongside one of the general servers: the general server handles build and run, StoreScreens handles the screenshot matrix at the end.

Each run produces a browsable HTML preview with per-device galleries:

When the MCP server is configured, the agent streams per-screenshot progress inline as each device captures:

<video src="https://github.com/user-attachments/assets/fb0c0cf1-8fdc-4e28-98c9-1baded6dd947" controls></video>