1. Upload the build
With the npm MCP on your computer,summer_publish_build (operation store.upload_file) uploads the file from your disk: a store bundle, a web build or a download. The first call shows what it will upload. Show it to the owner; the second call, with confirm: true, uploads it after they approve this exact file and version.
1. Preview
2. Upload
Store bundles upload in 64 MiB parts, web builds in 16 MiB parts. If the connection drops, call it again with the same file and version: it continues the same upload and skips the parts already stored.
Web builds and downloads are store versions, one per platform. A web
.zip is checked before upload: index.html at its root, at most 2,000 files and 500 MiB.
Without the npm MCP (a hosted agent that has the file elsewhere), run three operations with summer_call. They take one uploadId for every kind:
store.upload_beginwithgameId,kind(bundle,webordownload) andsizeBytes. It returns theuploadIdand the part plan.store.upload_sign_partswithgameId,uploadIdandparts. PUT each part to its URL with every returned header.store.upload_completewithgameIdanduploadId. It answers a job: wait withsummer_jobs_waituntil it isdoneorfailed.
2. Wait for the checks
summer_store_status shows every upload and its state: uploading, processing, checking, ready or failed. Summer checks a bundle on every platform it lists. A failed upload says what to fix; see Troubleshooting.
3. Look at it first (optional)
1h, 1d or 7d.
4. Check what is missing
summer_store_get_listing returns the publish checklist for each store. Fix everything it lists before you go live. Read it again after each change.
5. Go live
summer_go_live (operation store.go_live) takes the game live. The first call shows what will go live: the page and the build.
1. The plan
confirm: true:
2. Go live
It releases the build to every platform that passed its checks, publishes the store page, and watches until players get it. The game is live as soon as Summer’s automatic checks pass. There is no review to wait for. Web builds and downloads go live with the page.
live: the game is on Summer Games. Give the owner the page link.waiting: call it again to keep watching. WithwaitingOn: "summer", every check passed and Summer is finishing the launch: nothing to fix.- A failed check: it names the check and its fix. Fix it, upload again, and go live again.
needs_permission: Publish is off for agents on this account (Agent permissions). Ask the owner to click Publish in Studio.
Updates
Export again with a new version, upload it the same way, and go live again. Players keep the current version until the new one is live.Ask your agent
Upload my build and take it live. Your agent uploads, waits for the checks and asks you before it goes live.
Does this not help you? Reach out on Discord!

