Shipshots
Generate App Store and Play Store screenshot sets from your agent without leaving Claude Code or Cursor during launch prep.
Overview
Shipshots is a MCP server for the Launch phase that creates AI-generated App Store and Play Store screenshots through your coding agent via the Shipshots API.
What is this MCP server?
- MCP server (shipshots-mcp on npm) exposes Shipshots screenshot workflows to coding agents over stdio
- AI-assisted generation for both Apple App Store and Google Play Store formats
- Connects to a hosted Shipshots instance at shipshots.app via SHIPSHOTS_API_URL and dashboard MCP token
- Token-based auth: create SHIPSHOTS_API_TOKEN under Dashboard → Settings → MCP Tokens
- Versioned MCP package (0.6.1) with published server schema for agent registry compatibility
- MCP server schema version aligned with 2025-12-11 server.schema.json
- Published npm package identifier shipshots-mcp at version 0.6.1
- Two required environment variables: SHIPSHOTS_API_URL and SHIPSHOTS_API_TOKEN
What problem does it solve?
Polishing platform-specific store screenshots for iOS and Android listings is slow and easy to get wrong when you are shipping alone without a dedicated design workflow.
Who is it for?
Solo or indie builders who already have a mobile app or build close to submission and want agent-triggered, AI-generated store screenshots tied to Shipshots.
Skip if: Teams that only need web landing pages, do not publish to Apple or Google stores, or refuse to use a hosted API token for screenshot generation.
What do I get? / Deliverables
After you register shipshots-mcp and set your API token, your agent can produce store-ready screenshot sets aligned with App Store and Play Store listing needs.
- AI-generated screenshot sets formatted for App Store listings
- AI-generated screenshot sets formatted for Google Play Store listings
- Agent-callable screenshot workflow without leaving the IDE
Recommended MCP Servers
Journey fit
Store screenshots are produced when you are ready to publish or refresh iOS and Android listings, which maps to the Launch phase rather than earlier build-only work. Screenshots are a core App Store Optimization asset alongside titles and previews, so the canonical shelf is launch → aso.
How it compares
MCP integration to a hosted screenshot service, not an in-repo agent skill or static design template pack.
Common Questions / FAQ
Who is Shipshots for?
Shipshots is for solo builders and small teams shipping iOS or Android apps who want their Claude Code, Cursor, or similar agent to generate store listing screenshots through MCP instead of manual design exports.
When should I use Shipshots?
Use Shipshots during Launch and ASO work when you need new or updated App Store and Play Store screenshots before submission, a version bump, or a listing refresh.
How do I add Shipshots to my agent?
Add the shipshots-mcp npm MCP server to your agent config, set SHIPSHOTS_API_URL (typically https://shipshots.app) and SHIPSHOTS_API_TOKEN from Dashboard → Settings → MCP Tokens, then restart the MCP host so tools load over stdio.