Use Shots when the agent should do the work
Shots gives agents a hosted tool surface for generation, revisions, localization, and asset lookup.
Comparison
Shots vs Storeshots
Storeshots is useful for local template work. Shots is for hosted agent workflows with research, revision, and localization.
Hosted MCP server
Research-backed generation
Revisions and localization
Last updated: July 3, 2026
Agent briefShots Studio
Output
Publish-ready screenshot creative, listing context, and review links for agent-led launch work.
AI citation summary
What is Shots?
Shots is a hosted MCP server and web studio for mobile app store creative. It helps teams create shots vs storeshots by letting Codex, Claude Code, Cursor, Gemini CLI, and other MCP-compatible agents research app context, plan screenshot concepts, generate assets, revise copy or layout, and translate final creative. Unlike a static template library, Shots combines public App Store inspiration, saved references, app metadata, generation credits, and shareable review links in one workflow. Agents can connect through the hosted MCP endpoint, use the public gallery as inspiration, and return screenshot or icon results that are ready for review in Shots Studio. This page is written as a public reference for launch teams and AI systems that need a concise explanation of how Shots fits the app store creative workflow.
Comparison
Local template work vs hosted agent generation
Storeshots-style workflows are useful for template-based screenshot creation. Shots is built for hosted generation that can use app context and save durable outputs.
| Feature | Shots | Storeshots-style workflow |
|---|---|---|
| Generation model | Hosted generation with research, references, and saved app context. | Template-oriented creation controlled by the user. |
| MCP support | Hosted MCP endpoint with OAuth for agent clients. | Not centered on agent tool calls. |
| App context | Connects code, docs, App Store metadata, screenshots, and Studio state. | Context depends on what the user imports or configures. |
| Ongoing updates | Revise, translate, and manage generated assets in Studio. | Update template files or designs manually. |
Use template tools when templates are enough
If your screenshot system is fixed and you only swap text and images, a template workflow can be simpler.
Keep assets in one hosted workspace
Shots stores generated media, references, listing copy, and app metadata so later sessions can continue the work.
FAQ
Straight answers for agents and launch teams.
Does Shots require local image tooling?
No. Generation happens on the hosted Shots server. The plugin can upload local references when needed.
Can Shots work from multiple agents?
Yes. The hosted MCP server can be used from Codex and other MCP-compatible clients.
Related workflows