Design

launchshots.com

Generates finished App Store and Google Play screenshot sets from uploaded screenshots via the LaunchShots API.

1 endpoint5 known toolsFirst detected October 17, 2026Last detected October 17, 2026

ENDPOINT 1

https://www.launchshots.com/api/mcp

No auth detected

MCP server metadata

Name: launchshots
Version: 1.0.0

Capabilities

tools.listChangedprompts.listChanged

Server instructions

LaunchShots turns an app's raw screenshots into a finished, fully editable App Store / Google Play screenshot set: per-screen marketing headlines, palette, device frames and layout, in three art directions to choose from. 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.

Known tools 5

prepare_screenshot_upload

Start a screenshot set and get one upload URL per screenshot.

Potential side effects

generate_screenshot_set

Design a finished App Store / Google Play screenshot set from uploaded screenshots.

Inferred read-only

get_screenshot_set

Check on a screenshot set, waiting up to wait_seconds for it to finish.

Inferred read-only

get_account

Show which LaunchShots account this connection uses and how many generations it has left.

Inferred read-only

list_projects

List the most recently edited projects in this API key's LaunchShots account, with a link to open each in the editor.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.launchshots]
url = "https://www.launchshots.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "launchshots": {
      "type": "http",
      "url": "https://www.launchshots.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: launchshots
Remote MCP URL: https://www.launchshots.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "launchshots": {
      "url": "https://www.launchshots.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "launchshots": {
      "type": "http",
      "url": "https://www.launchshots.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "launchshots",
  "transport": "streamable-http",
  "url": "https://www.launchshots.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.