MobileScreen MCP - Your coding agent now designs your App Store screenshots

Turn raw simulator captures into App Store and Google Play screenshot sets. 2.0 rebuilds the design engine: it measures your brand colors, commits to one of seven looks, writes a headline per screen and transcreates it into 50 languages with real font fitting. New MCP server: Claude Code, Cursor or Codex generate the set, edit any word or device, look at the renders and export to fastlane. Then push to App Store Connect with name, subtitle and keywords.

Add a comment

Replies

Best
Hey Product Hunt šŸ‘‹ I'm Furkan. I build iOS apps, and every release ended the same way: the app was done, the store screenshots weren't. We launched MobileScreen here earlier this year and you were honest with us: a paywall before you could try it, and sets that looked repetitive. So we rebuilt it: → It measures your brand colors from your pixels and commits to one of 7 looks for the whole set → Headlines are transcreated into 50 languages and fitted with real font metrics (RTL and CJK too) → New MCP server: Claude Code, Cursor or Codex can generate the set, change any word or device, look at the renders and export straight into fastlane → Send the set to App Store Connect, with name, subtitle and keywords edited next to the screenshots Every set in the gallery was made with MobileScreen from plain simulator captures. You can try it free on your own app. One question for you: which part of your store listing would you never hand to an AI? šŸ‘‡

Screenshots are always the last thing before a release for me too, and they always take longer than the feature did. The fastlane export plus the App Store Connect push is the part I'd actually use, since that's where the manual slog lives. Curious how far the MCP loop goes — does the agent look at the renders and fix its own bad crops, or is the review step still on me? Generating the set from simulator captures instead of hand-laying-out screenshots is a big time save either way.