Rork launches Max Publishing to auto-fill App Store listings and submit builds
Rork added Max Publishing to generate icons, screenshots, listing text, review metadata, and submission steps for App Store releases, and also shipped an App Store MCP. Use it first on non-critical apps and keep a manual review gate.

TL;DR
- Rork launched Max Publishing, which it says can complete an App Store submission end to end: filling listing fields, generating icons and screenshots, creating a "mock review," and submitting the app without manual form work, as shown in the launch post.
- The same rollout also included an App Store MCP, with Rork stating simply that it "built App Store MCP," suggesting the submission flow is being exposed through an MCP-style integration rather than only a point feature.
- The product pitch is explicitly about cutting release overhead from hours to minutes, with the reposted launch copy in the supporting post framing it as AI that submits apps "in minutes, not hours."
- Early user reactions in one practitioner repost focus on the operational pain point rather than design polish: "the most annoying part of shipping an app just disappeared," after Rork handled the full submission flow.
What shipped
Rork's new Max Publishing feature is aimed at the last mile of iOS shipping: App Store Connect metadata and submission packaging. In the main announcement, the company says the tool now "fills in all the fields," generates "icons & screenshots," adds a "mock review so you don't get rejected," and then submits the build. The attached submission demo shows an App Store form being populated automatically, followed by generated visual assets and a final submitted state.
The scope is broader than text generation. Rork specifically calls out "Yes, iPad screenshots too" in the launch post, which matters because screenshot production and device coverage are often the most repetitive parts of release prep. A repost of the launch copy in the supporting thread also frames the feature as reducing submission time from hours to minutes.
How it works and where it fits
Rork followed the launch by saying "We built App Store MCP," which is the clearest implementation detail in the evidence about how this may plug into agentic workflows. Based on the launch behavior shown in the demo post, the MCP angle likely gives an AI client structured access to App Store publishing steps instead of treating submission as a one-off UI automation.
There is also some product context around why Rork is leaning into publishing automation now. In a reposted note, Rork says its own iOS app is "no longer on the App Store" and adds that it has now made it easy to "build Rork in Rork and publish to the App Store," positioning submission as part of a fuller build-to-release loop. Early reactions are positive but still anecdotal: one user repost says Rork completed their submission, while another repost summarizes the launch as automating "literally everything" in the listing flow.