Launch Shots is an MCP server published by com.launchshots, hosted at www.launchshots.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 5 tools, including prepare_screenshot_upload, generate_screenshot_set, get_screenshot_set, get_account, list_projects.
Turn your app's screens into editable App Store and Google Play screenshot sets, from your agent.
895 connections through 4 shared values. Tap any node.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
| Parameter | Type | Description |
|---|---|---|
| screenshot_count * | integer | How many screenshots you will upload (1–10; 3–8 makes the best set). |
{
"name": "prepare_screenshot_upload",
"title": "Prepare screenshot upload",
"description": "Start a screenshot set and get one upload URL per screenshot. Step 1 of 3.\n\nPick 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.\n\nUpload 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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"screenshot_count"
],
"properties": {
"screenshot_count": {
"type": "integer",
"maximum": 10,
"minimum": 1,
"description": "How many screenshots you will upload (1–10; 3–8 makes the best set)."
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}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 — each a different angle on the app with its own headlines, layouts, type and palette — all 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.
| Parameter | Type | Description |
|---|---|---|
| set_id | string | The set_id from prepare_screenshot_upload, once its screenshots are uploaded. |
| app_name * | string | The app’s name as it appears in the store. |
| language | string | Store language to write the headlines in, e.g. en-US, de-DE, ja, pt-BR. Defaults to en-US. |
| platform * | string | ios for the App Store, android for Google Play. |
| style_note | string | Optional art direction, e.g. "dark and premium", "playful, uses our brand orange #FF6B00". |
| screenshots | array | Only if you cannot upload with prepare_screenshot_upload: the screenshots inline, each under ~1 MB. |
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 and the three directions, each with the headlines it wrote for every screen. 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.
| Parameter | Type | Description |
|---|---|---|
| set_id * | string | The set_id (ls_set_…). |
| wait_seconds | integer | How long to wait for a set that is still generating (0–50, default 45). |
{
"name": "get_screenshot_set",
"title": "Get screenshot set",
"description": "Check on a screenshot set, waiting up to wait_seconds for it to finish. Step 3 of 3.\n\nWhen it is ready this returns the review link and the three directions, each with the headlines it wrote for every screen. 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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"set_id"
],
"properties": {
"set_id": {
"type": "string",
"maxLength": 80,
"description": "The set_id (ls_set_…)."
},
"wait_seconds": {
"type": "integer",
"maximum": 50,
"minimum": 0,
"description": "How long to wait for a set that is still generating (0–50, default 45)."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}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.
No parameters.
{
"name": "get_account",
"title": "Get account",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | How many to return (default 10). |
{
"name": "list_projects",
"title": "List projects",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "How many to return (default 10)."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}LaunchShots turns an app's raw screenshots into a finished, fully editable App Store / Google Play screenshot set, in three art directions to choose from — three different designs, each with its own per-screen marketing headlines, layouts, palette and device frames. Workflow: 1. Collect 3–8 screenshots of the app's most important screens, populated with realistic data (no empty states, login walls, debug banners or placeholder text). Capture them from a simulator/emulator if needed. 2. Call prepare_screenshot_upload with the count, then PUT each file to its upload URL (curl commands are provided). If you cannot run shell commands, pass small screenshots inline to generate_screenshot_set instead. 3. Call generate_screenshot_set with the set_id, the app name, a specific description (what it does, who it's for, what makes it different — read the README / store copy) and the platform. 4. Call get_screenshot_set to wait for it (about 1–2 minutes). Then give the user the review link: they pick a direction and it opens in the LaunchShots editor, where every headline, color and frame stays editable and exports at every store size. Without an API key the server works on the free tier (a few sets a day, from a shared daily allowance) and the user signs up free to keep the set. With an API key (Authorization: Bearer ls_key_…) sets are charged to that account: 3 free generations, then 1 credit each or unlimited on a plan. Call get_account to see what is left.
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.
| include_tablet | boolean | Also produce the matching iPad / Android tablet set. Counts as a second generation; needs an API key. |
| app_description * | string | What the app does, who it is for and what sets it apart — 2–6 specific sentences drawn from the README, store listing or product copy. |
{
"name": "generate_screenshot_set",
"title": "Generate screenshot set",
"description": "Design a finished App Store / Google Play screenshot set from uploaded screenshots. Step 2 of 3.\n\nReturns 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 — each a different angle on the app with its own headlines, layouts, type and palette — all fully editable in the LaunchShots editor.\n\nWrite 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.\n\nEither 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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"app_name",
"app_description",
"platform"
],
"properties": {
"set_id": {
"type": "string",
"maxLength": 80,
"description": "The set_id from prepare_screenshot_upload, once its screenshots are uploaded."
},
"app_name": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "The app’s name as it appears in the store."
},
"language": {
"type": "string",
"maxLength": 32,
"description": "Store language to write the headlines in, e.g. en-US, de-DE, ja, pt-BR. Defaults to en-US."
},
"platform": {
"enum": [
"ios",
"android"
],
"type": "string",
"description": "ios for the App Store, android for Google Play."
},
"style_note": {
"type": "string",
"maxLength": 500,
"description": "Optional art direction, e.g. \"dark and premium\", \"playful, uses our brand orange #FF6B00\"."
},
"screenshots": {
"type": "array",
"items": {
"type": "object",
"required": [
"data_base64"
],
"properties": {
"data_base64": {
"type": "string",
"maxLength": 2000004,
"description": "The image file, base64-encoded (no data: prefix)."
}
}
},
"maxItems": 10,
"minItems": 1,
"description": "Only if you cannot upload with prepare_screenshot_upload: the screenshots inline, each under ~1 MB."
},
"include_tablet": {
"type": "boolean",
"description": "Also produce the matching iPad / Android tablet set. Counts as a second generation; needs an API key."
},
"app_description": {
"type": "string",
"maxLength": 4000,
"minLength": 1,
"description": "What the app does, who it is for and what sets it apart — 2–6 specific sentences drawn from the README, store listing or product copy."
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}