LaunchShots turns an app's raw screenshots into editable App Store and Google Play screenshot sets, with headlines, frames and three art directions.
What you can do
Start a screenshot set and get one upload URL per screenshot, then upload the app's key screens
Design a finished store screenshot set from the uploaded screens, returning a review link while it works in the background
Check on a set, waiting for it to finish, and return the review link, per-screen headlines and three art directions
Show which LaunchShots account the connection uses and how many generations remain
List recently edited projects in the account with links to open them in the editor
When to use it
Useful when preparing store listings for an iOS or Android app and you want marketing-ready screenshot sets generated from a handful of real app screens, then refined by hand in the LaunchShots editor.
Requirements
Remote streamable HTTP endpoint; no local runtime needed. Works without an API key on a free tier, or with an API key sent as an Authorization Bearer header to charge sets to an account. Uploading files needs the ability to send HTTP PUT requests, or small screenshots can be passed inline.
Before you install
Uploaded screenshots and app details are sent to a third-party service. With an API key, sets are charged to that account: 3 free generations, then 1 credit each or a plan, so generation spends credits. The API key is a secret and should be kept out of shared logs. Generated sets are reviewed and edited by the user through a link.
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/com.launchshots%2Flaunchshots/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.
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.
Parametersscreenshot_countrequired
generate_screenshot_set
Generate screenshot set
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.
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.
Parametersset_idrequiredwait_seconds
get_account
Get account
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.
Takes no parameters.
list_projects
List projects
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.
Parameterslimit
Version history
1
v1.0.0LatestOct 29, 2026
Score
83%
83% 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 listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.