https://docs.summerengine.com/publishing/agent-checklist.md.
Never say the game is published, in review or live. You stop at the approval link. The owner approves.
0. Connected
- The hosted MCP answers:
summer_store_list_gamesreturns a list (it may be empty). - On the owner’s computer: the npm
summer-engineMCP lists thesummer_store_*tools. If it shows onlysummer_store_tools, the owner runssummer login --storeonce. - If either fails, give the owner the steps on Connect your agent and stop.
1. The game
-
summer_list_projects, thensummer_get_project: the project and its board id. - Read the project: genre, main scene, single-player or multiplayer, platforms it is built for.
- Ask the owner only what the project does not say: platforms, price.
2. The store game
-
summer_store_list_games. If the game is there, use itsgameId. - Otherwise
summer_store_create_gamewith the title andtargets.- Web, Mac, Windows, Linux →
web,macos-universal,windows-x64,linux-x64(desktop store). - iPhone, Android →
ios,android(mobile store).
- Web, Mac, Windows, Linux →
-
summer_store_get_listing: note the stores, the empty slots and the checklist.
3. Analytics (before export)
- Optional. If the owner wants events, add 3-10 with the
summer-analyticsskill. Fire and forget, no personal data. See Analytics in Grow.
4. Text
-
summer_store_update_listing:- desktop
tagline(up to 80),description(120-300),tags(3-8 store categories); - mobile:
mobileSameAsDesktop: trueif it fits 120-170, else its owntaglineanddescription; contentRatingandcontentDescriptors.
- desktop
- Only what the game really has. No filler phrases, no prices.
- Rules: Store page text.
5. Art
For each empty required slot of each store the game is on:- Look in My assets first:
summer_list_my_assets,summer_search_assets. - If nothing fits, read the board’s look (
summer_board_game_soul) and make it:summer_generate_image,summer_check_job. - Crop to the slot’s exact shape, subject at the focal point. See Make store art.
- Upload the crop:
summer_upload_image_begin, POST the file,summer_upload_image_complete→assetId. -
summer_store_set_artwith the slot, theassetIdand afocalPoint. - Screenshots are real gameplay: capture with the engine or ask the owner. Desktop 4-6, mobile 3-5.
- No text in key art, the tall cover, icons or screenshots. At most 20 pictures in total.
- Slot table: Store art.
6. Export
- Pick the build per platform: Export your game.
- Web or download:
summer_export_templateslist, theninstallwhat is missing. -
summer_export_gamewithtargets(andformat: "download"for web, Mac or Windows downloads). - The result lists the right platforms and a main scene.
7. Upload
- Each export:
summer_publish_buildwithgameIdand a newclientVersion(web builds and downloads take theirplatformfrom the export). Show the owner the preview; call again withconfirm: trueafter they agree. - On a game that is already live, a web build or download is finished by the owner in Studio.
-
summer_build_status(orsummer_store_version_status) saysready. Onfailed, fix and upload a new version.
8. Check
-
summer_store_get_listing: the checklist has nothing missing. - Optional:
summer_store_preview_linkand show the owner.
9. Submit and hand over
-
summer_store_submitwith the build, the price the owner asked for (priceUsdCents,0= free) and a shortnote. - Give the owner the
approvalUrland say: “Open this link and click Approve publishing. Summer reviews it next.” - Stop.
After the owner approves
-
summer_store_get_listingshows the approval as approved. - Summer staff review the page. When the review passes, the game goes live. No second click.
- If the approved store bundle is not yet what players get,
summer_build_releasereleases exactly that build. - If the approval is Stale, read the listing again and submit again.
- Later:
summer_grow_overviewfor the numbers.
Does this not help you? Reach out on Discord!

