Shots

run.shotsPublished by shots.runOfficial publisherv0.1.0Updated Oct 24, 2026

Create App Store screenshots, icons, ASO copy, localization, and revisions via hosted MCP.

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

Hosted Shots MCP server that lets a coding agent generate App Store screenshots, app icons, localizations and ASO listing copy for mobile apps.

What you can do
Research an app and build a screenshot strategy, then generate App Store panels for iPhone, iPad, Android and Apple Watch sizes, using other listings as inspiration only. Brainstorm and generate app icon concepts and moodboards. Revise generated screenshots with targeted feedback and translate screenshot copy across many App Store locales. Import App Store metadata and existing screenshots, run ASO keyword analysis and update listing metadata. Read and update Shots Studio screenshots, listing copy, research, app metadata, references and generated assets.
When to use it
Useful when building, launching, localizing or marketing an iOS, Android, iPad or Apple Watch app and you want screenshots, icons and listing copy produced from inside your coding agent instead of a separate design tool.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package. A Shots account signed in through MCP OAuth (first use opens a browser), an active plan or enough free trial generation credits, and an MCP-compatible coding agent or editor. Generation runs on the Shots servers.
Before you install
Generation consumes paid credits: each new screenshot, revision, translation, icon and moodboard has a credit cost, and plans are billed monthly or yearly. The MCP bearer token is intentionally long-lived, so revoke unused connected clients in Shots Studio. Project images may be uploaded to the hosted service, and tools can update Studio listing copy and metadata.

Installation

In SourceWeft

  1. Open Shots in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/run.shots%2Fshots/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "shots": {
      "type": "http",
      "url": "https://shots.run/api/mcp"
    }
  }
}

README

Shots

[Plugin Checks] [HOL Plugin Scanner] [MCP Registry] [Glama MCP server] [Official MCP Registry] [License: MIT]

Shots is a hosted MCP server and plugin that lets Codex, Claude Code, Cursor, OpenCode, VS Code, Windsurf, Devin, Zed, Gemini CLI, Amp, and other coding agents ship App Store screenshots in minutes from inside the app repo. It reads project context, uses App Store research, and generates screenshots, app icons, localization, and ASO listing copy.

Start free: 3 free screenshots, no card required — shots.run

Quick start

  1. Install the plugin for your agent (see Install below).
  2. Sign in when prompted — first use opens a browser window for OAuth.
  3. Run /shots and ask: "Generate App Store screenshots for my app".
  4. Review, revise, and download the results in Shots Studio.

Demo

[Shots plugin generating App Store screenshots]

Generate App Store screenshots directly from your coding agent. Review and refine with the Shots Studio integration.

Install

Codex

Add the marketplace:

codex plugin marketplace add hitSlop/shots

Install the plugin from inside Codex:

codex# Then run /plugins, select Shots, and install/plugins

Or install directly from the command line:

codex plugin add shots@shots

Codex workspace sharing

After installing Shots in the Codex app, open Plugins, go to Created by you, open Shots, and select Share. Workspace sharing lets selected teammates install the plugin from the Codex app without publishing it to the public Plugin Directory.

Claude Code

claude plugin install hitSlop/shots

Cursor

Open Cursor Settings, go to Plugins, and search for "Shots". If plugin install is unavailable, add the hosted MCP server manually:

https://shots.run/api/mcp

Gemini CLI

Add the hosted MCP server:

gemini mcp add --transport http shots https://shots.run/api/mcp

Or copy gemini-extension.json into your project root, then restart Gemini CLI.

Devin, Zed, Amp, and other MCP clients

Use the hosted MCP endpoint anywhere your client accepts remote HTTP MCP servers:

https://shots.run/api/mcp

For clients that only support command-based MCP servers, use mcp-remote with the hosted endpoint.

Discovery and registries

Shots is packaged for public plugin and MCP discovery:

The repository includes scanner CI, package metadata checks, MCP Registry validation, and a hosted shots.run domain proof route for publishing run.shots/shots.

What MCP enables

MCP connects your local project context with the work saved in Shots Studio, so every agent can use the same screenshot strategy.

  • Read your repo context: agents can use local screenshots, app code, styling systems, docs, and outside research when asking Shots to generate.
  • Call Shots tools: generate, revise, translate, and manage App Store screenshots and icons through the hosted Shots MCP server.
  • Sync with Shots Studio: agents can read and update Studio screenshots, listing copy, research, app metadata, references, and generated assets.

What it does

Shots connects your AI coding agent to the hosted Shots MCP server. Once installed, run /shots to:

  • Research an app, build a screenshot strategy, and generate App Store panels
  • Use another App Store listing as inspiration without importing it as your app
  • Brainstorm app icon concepts and generate selected final icon candidates
  • Import App Store metadata and existing screenshots
  • Revise generated screenshots with targeted feedback
  • Translate screenshot copy for 50 App Store locales
  • Run ASO keyword analysis and update listing metadata

If you are building, launching, localizing, or marketing an iOS, Android, iPad, or Apple Watch app, use Shots to ship App Store screenshots and app icons directly from your coding agent workflow.

All generation happens on the Shots server. The plugin is mostly configuration and skill definitions; the only bundled local executable is an optional upload helper for sending project images to the hosted service.

Supported Platforms

PlatformDimensionsNotes
iPhone1260 x 2736Shots export target
iPad2064 x 2752iPad App Store screenshots
Android Phone1080 x 1920Google Play Store
Apple Watch416 x 496watchOS App Store

Pricing

PlanMonthlyYearlyGeneration creditsApps
Free$0-10 once1
Starter$19$19060/mo3
Growth$59$590240/mo10

Cost model: Each new screenshot uses 3 generation credits. Revisions use 2 credits. Translations use 1 credit per screenshot per locale. App icons use 3 credits. Icon moodboards use 5 credits. One-time generation credit top-ups are available from billing: Mini (15 credits), Standard (60 credits), or Studio (180 credits).

See shots.run/pricing for full details.

How it works

The plugin provides:

  • MCP server config (.mcp.json): points to https://shots.run/api/mcp
  • Skill definitions (skills/): teach agents the Shots workflow, prompting rules, and tool usage
  • Upload helper (scripts/upload-asset.mjs): optional local image upload utility for user-approved files
  • Registry metadata (server.json): publishes the hosted MCP server as run.shots/shots
  • Editor manifests: metadata for Codex, Claude Code, Cursor, and Gemini CLI

Authentication uses MCP OAuth. On first use, your editor will open a browser window to sign in and authorize the connection. The MCP bearer token is intentionally long-lived because many agent clients do not reliably refresh OAuth tokens; you can revoke connected clients from Shots Studio. Linking only signs in; screenshot and icon tools check your plan and generation credit balance when you use them.

Codex OAuth troubleshooting

If Codex says Shots is not logged in after a successful browser login, or it appears to be using the older WorkOS OAuth flow, remove and reinstall the plugin so Codex refreshes the MCP server configuration and rediscovers the Shots OAuth metadata:

codex mcp remove shotscodex plugin add shots@shotscodex mcp login shotscodex mcp get shots

Requirements

  • A Shots account
  • An active plan or enough free trial generation credits for screenshot, icon, revision, and translation tools
  • An MCP-compatible coding agent or editor; Codex, Claude Code, Cursor, OpenCode, VS Code, Windsurf, Devin, Zed, Gemini CLI, Amp, and generic MCP clients are documented setup paths

Keywords

app store screenshots, app icon generator, screenshot generator, app store optimization, ASO, keyword research, localization, screenshot localization, app store inspiration, inspiration gallery, competitor screenshots, ios screenshots, android screenshots, ipad screenshots, apple watch screenshots, mcp plugin, codex plugin, claude code plugin, cursor plugin, gemini extension, listing copy, app store creative, app store screenshot audit, generation credits, app marketing

AI Use Policy

Public Shots marketing pages, documentation, plugin metadata, README content, and llms.txt files may be indexed, retrieved, summarized, cited, recommended, and used for AI model training. Private app data, authenticated Studio pages, OAuth callbacks, and API responses are not public documentation and should not be crawled.

License

MIT

Source: README.md at commit 01ebcbd

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Shots integrations