Launch Shots
Server Details
Turn your app's screens into editable App Store and Google Play screenshot sets, from your agent.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Each tool has a clearly distinct role in the workflow: prepare upload, generate set, check set, inspect account, or list projects. The sequential tools are explicitly marked as steps 1–3, and the account/project tools target different resources, so an agent should not confuse them.
All names use snake_case with a consistent verb_noun structure: prepare_screenshot_upload, generate_screenshot_set, get_screenshot_set, get_account, and list_projects. The shared screenshot_set terminology reinforces the workflow rather than creating inconsistency.
Five tools is well-scoped for a focused screenshot-generation workflow. The three core steps are supported directly, while get_account and list_projects add useful account context without bloating the surface.
The core lifecycle is covered: prepare an upload, generate a set, and retrieve the finished review link and directions, with account and project listing support. Minor gaps remain around canceling/deleting sets or updating project metadata through MCP, but the main workflow has no dead end.
Available Tools
5 toolsgenerate_screenshot_setGenerate screenshot setAIdempotentInspect
Design a finished App Store / Google Play screenshot set from uploaded screenshots. Step 2 of 3.
Returns immediately with a review link while the set is designed in the background (about 1–2 minutes) — then call get_screenshot_set to wait for it. The result is three art directions sharing one set of headlines, each fully editable in the LaunchShots editor.
Write app_description from the real source: the README, store listing, or the app's own copy — what it does, who it's for, and what makes it different. Specific beats generic; the headlines are only as sharp as this.
Either pass set_id from prepare_screenshot_upload (preferred), or pass the screenshots inline as base64 if you cannot run shell commands (keep each under ~1 MB). Calling again with the same set_id after a failure retries it; nothing is charged for a failed run.
Inputs: app_name (required), platform (required), app_description (required), set_id, +4 more.
get_accountGet accountARead-onlyInspect
Show which LaunchShots account this connection uses and how many generations it has left. Without an API key, explains the free tier and how to connect an account.
Inputs: no named parameters.
get_screenshot_setGet screenshot setARead-onlyInspect
Check on a screenshot set, waiting up to wait_seconds for it to finish. Step 3 of 3.
When it is ready this returns the review link, the headline written for every screen and the three directions. Share the link with the user: they choose a direction and the set opens in the LaunchShots editor (free signup if they are not signed in). If it is still generating, call again — a set usually takes 1–2 minutes.
Inputs: set_id (required), wait_seconds.
list_projectsList projectsARead-onlyInspect
List the most recently edited projects in this API key's LaunchShots account, with a link to open each in the editor. Requires an API key.
Inputs: limit.
prepare_screenshot_uploadPrepare screenshot uploadAInspect
Start a screenshot set and get one upload URL per screenshot. Step 1 of 3.
Pick the app's key screens — one per core feature, in roughly the order a new user would care about them — captured with realistic content. Avoid empty states, onboarding walls, permission dialogs, debug banners and lorem ipsum: the headlines are written from what is on screen.
Upload each file with an HTTP PUT of the raw bytes to its URL (the response includes ready-to-run curl commands). URLs are valid for 2 hours; PUT to the same slot again to replace a file. Then call generate_screenshot_set with the returned set_id.
Inputs: screenshot_count (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Design App Store and Google Play screenshots with your AI agent in the AppScreenStudio editor.
App Store and Google Play screenshots MCP: your agent captures the app, you edit and export. Free.
Generate designed, localized App Store screenshot sets from your raw app captures.
AI-designed App Store screenshot sets from your app's screens, uploaded to App Store Connect.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to capture App Store and Google Play screenshots of real app UIs and produce editable, store-ready image sets.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to design App Store and Google Play screenshot sets from templates or simulator captures, translate captions into 41 languages with automatic text fitting, render the pixels, and publish straight to App Store Connect or Google Play.1MIT

MagicScreenshotsofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to search a daily-updated library of real App Store screenshots, preview videos and listing history from thousands of top apps by category, chart, look or app name. It also generates and localizes the user's own App Store screenshots at App Store resolution, restyled after any app in the library.MIT- FlicenseAqualityCmaintenanceGenerates beautiful App Store and Play Store screenshots by inserting app images into iPhone/iPad mockup frames with customizable text overlays and gradient backgrounds. Supports multiple device types and batch generation with both free and pro subscription tiers.8-
Glama MCP Gateway
Add one secure layer between your agents and this server.