Start

Store-ready screenshots from your agent

See what ShotOps makes, choose between Local and Hosted MCP, and take the shortest path to your first App Store preview.

View as Markdown

ShotOps turns raw app screenshots into styled App Store panels, an ordered strip, and a screenshot bundle shaped for fastlane deliver. You ask for the outcome in words; your agent uses the MCP tools behind the scenes.

See the whole pipeline in one page for how every stage connects, end to end, before diving into any one of them.

#What ShotOps makes

Start with the PNGs you already have. ShotOps places them in 3D device mockups, adds the captions you provide, and composes the panels at App Store sizes.

Five raw weather app screens from the landing-page parallax rail, shown without device frames. — Five raw Tidebook screens before device frames, captions or panel composition.

Stage two App Store strip preview: five weather screenshots rendered inside phone devices on framed panels with captions. — The same screens as a low-resolution preview strip, ready for a quick design decision.

A preview lets you settle the design. Store-ready output gives you full-resolution panels and a screenshot bundle you upload with your own fastlane. ShotOps never holds an Apple or store credential.

#Choose where ShotOps runs

Both connections use the same tools and render engine. Choose by where your screenshots are and who should provide the compute.

Choose	When it fits	Start here
Your computer · Local MCP	The screenshots are on this machine, you want local rendering, or you want the simplest first preview.	Connect Local MCP
ShotOps Cloud · Hosted MCP	You are using ChatGPT or CI, need browser sign-in, or do not want to run the renderer on your computer.	Connect Hosted MCP

You can use both with the same ShotOps account. Signing in does not decide where rendering happens.

#Render your first preview

The shortest path is Local MCP: connect it, point at the Tidebook PNGs, then ask:

Turn these five Tidebook screenshots into an App Store preview. Use the filenames for their order, add the headlines I supplied, and show me the result before making store-ready files.

Render your first preview walks through that one safe path. You finish with a complete low-resolution strip and one deliberate revision. You do not need an account, cloud credits, an Apple ID, or the full tool catalog.

In ChatGPT there is no shell and no disk to point at, so connect Hosted MCP instead. The shortest path there moves no files at all: sign in at shotops.dev, drop the raw screenshots into a project, set its screenshot storage to Your account, and “render my Tidebook project” becomes one call with nothing attached. Connect Hosted MCP sets that up, covers the attachment and URL forms, and finishes with the same first preview.

#Continue to store-ready output

Once the preview is approved:

Work on a saved project keeps the design editable after the conversation ends.
Plans and output explains the production entitlement, Hosted cloud credits and the difference between a preview and a deliverable.
Ship every locale renders the approved design with each locale's words and packages the folders together.
Tool reference is the generated source for exact calls, inputs, results and refusals.

Use the glossary when a result mentions a ref, delivery URL, readiness finding or waiver. Use Troubleshooting when the observed result is a refusal or a failed connection.