ShipScreens MCP Server
Automate App Store and Play screenshot capture, sizing, and release prep from Claude Code or Cursor via MCP or the ShipScreens CLI.
Overview
io.github.iamjamb/shipscreens is a Ship-phase MCP server (v0.1.6) for coding-agent screenshot release operations via npx stdio or CLI—not translation-only workflows.
What is this MCP server?
- MCP via npm: npx shipscreens mcp serve (stdio transport, v0.1.6)
- Explicitly for coding-agent screenshot release ops—not translation-only workflows
- Pairs MCP with ShipScreens agent CLI documented at shipscreens.com/tools/agent-cli/
- Registry precheck tooling shipscreens-registry-precheck meta v0.1.6
- GitHub repo iamjamb/shipscreens with published npm package identifier shipscreens
- Package/version: shipscreens 0.1.6
- Transport: stdio via npx mcp serve
- Documented exclusion: not for translation-only workflows
What problem does it solve?
Store screenshots bottleneck your ship date because manual capture and resize work does not scale across devices and release iterations.
Who is it for?
Solo mobile or cross-platform builders using Claude Code or Cursor who want agent-driven screenshot release ops tied to ShipScreens.
Skip if: Teams that only need string translation/localization without screenshot automation, or products with no app-store visual requirements.
What do I get? / Deliverables
Your agent runs ShipScreens MCP or CLI commands to operationalize screenshot release tasks as part of your submission checklist.
- Configured ShipScreens MCP stdio server in your agent
- Agent-driven screenshot release workflow
- Store-ready screenshot batches aligned to submission
Recommended MCP Servers
Journey fit
Screenshot release ops land in Ship when you are packaging store assets and tightening launch readiness right before or during submission. Store screenshot pipelines are classic launch prep—distinct from translation-only localization workflows called out in the server description.
How it compares
Screenshot release MCP/CLI, not a generic design skill or pure i18n translation server.
Common Questions / FAQ
Who is io.github.iamjamb/shipscreens for?
Indie developers and small teams using coding agents to prep App Store and Play screenshot assets during release.
When should I use io.github.iamjamb/shipscreens?
Use it in the ship/launch window when you need repeatable screenshot capture and release ops—not when you only need translation files.
How do I add io.github.iambenslater/shipscreens to my agent?
Install the npm package shipscreens (v0.1.6) and configure stdio MCP with arguments: npx shipscreens mcp serve; see shipscreens.com/tools/agent-cli/ for CLI parity.