Storeshots MCP Server

Render store-ready App Store and Google Play screenshots: device frames, headlines, exact sizes.

Local serverstdio

What is the Storeshots MCP server?

Connect Storeshots to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Render store-ready App Store and Google Play screenshots: device frames, headlines, exact sizes. The storeshots mcp server is what makes that connection.

What the server does

storeshots-mcp turns raw app screenshots into finished store-listing visuals — device frames, benefit-driven headlines, brand backgrounds, and exact store dimensions for iOS and Android. It runs as an MCP server, so the AI agent you already use writes and translates the copy while storeshots renders the pixels. No design tool, no subscription, no API keys.

Installation

storeshots-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • list_presets — List every preset with its store and exact dimensions
  • compose_screenshot — Render one screenshot (background, frame, headline, source image)
  • generate_set — Batch-render an ordered set for one platform + language; supports panoramas
  • create_showcase — Stitch generated screenshots into one preview strip
  • validate_screenshot — Check an image against store dimension and format rules

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Storeshots's toolset — list_presets, compose_screenshot, generate_set and 2 more — is a fair guide to whether it matches your workflow. It is maintained by mtbun; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
list_presetsList every preset with its store and exact dimensions
compose_screenshotRender one screenshot (background, frame, headline, source image)
generate_setBatch-render an ordered set for one platform + language; supports panoramas
create_showcaseStitch generated screenshots into one preview strip
validate_screenshotCheck an image against store dimension and format rules

How to install the Storeshots MCP server

{
  "mcpServers": {
    "storeshots": {
      "command": "npx",
      "args": ["-y", "storeshots-mcp"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Storeshots to list presets.
  • Use Storeshots to compose screenshot.
  • Use Storeshots to generate set.

Frequently asked questions

It connects Storeshots to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (list_presets, compose_screenshot, generate_set, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Storeshots directly.