https://docs.summerengine.com/publishing/agent-checklist.md.
Operations with their own tool are named summer_<area>_<action> (summer_games_list). Run any other operation with summer_call: {"op": "games.create", "input": {...}}. Every input: Operations.
Read status on every answer. done: it happened. running: wait with summer_jobs_wait. needs_approval: give the owner approval.url, then summer_jobs_wait with job.id. Never say the game is live until summer_store_status says so.
In the version of Summer made for Claude’s connector directory (
https://mcp.summerengine.com/directory), the tools keep their 3.x names (summer_store_list_games, summer_store_submit, summer_build_release) and there is no art generation: use My assets or upload the owner’s art. The version made for ChatGPT (https://mcp.summerengine.com/chatgpt) cannot publish. Use the full server, https://mcp.summerengine.com/mcp.0. Connected
-
summer_whoamianswers with the owner’s account. -
summer_games_listreturns a list (it may be empty). - On the owner’s computer, the npm MCP is set up (
npx -y summer-engine@latest setup <agent> --yes) and signed in (summer login). - If any of these fails, give the owner the steps on Connect your agent and stop.
1. The game
-
summer_projects_list, thenprojects.get: the project and its plan (planId). - 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. 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.
3. The store game
-
summer_games_list. If the game is there, use itsgameId. - Otherwise
games.createwithtitleand the listingtargetsfrom this table. -
summer_store_get_listingwithgameId: note the stores, the empty slots and the checklist.
The store saves
macos-universal and windows-x64 as the platforms macos and windows. So a store bundle for macos and windows serves the macos-universal and windows-x64 listing targets. You never need a download for a platform the bundle already covers. iPhone and Android open the mobile store; the other targets open the desktop store.
4. Export
Export first: a build that does not export stops the whole run, so find out before you make art.- Summer Engine is 0.7.0 or later.
summer doctorwarns when it is older;summer install --yesupdates it. - Web or download:
summer_export_templateslist, theninstallwhat is missing. -
summer_export_gamewith thetargetsfrom the table above. - The result lists the right platforms and a main scene.
- On failure, read the engine’s
ERROR:lines in the result. Hosted games: see Export your game. - Hosted games: the server pack starts the server scene, not the title. Run check 1 of the release readiness checklist and go through its other checks with the owner.
5. Art
For each empty required slot of each store the game is on:- Look in My assets first:
summer_assets_searchwithscope: "mine", thenscope: "library". - If nothing fits, read the plan’s saved direction (
plans.directionswithplanId) and make it:summer_assets_generate_imagewith the slot’saspectRatio, thensummer_jobs_wait. - Crop to the slot’s exact shape and minimum size, subject at the focal point. See Make store art.
- Upload the crop:
assets.upload_begin, POST the file,assets.upload_complete(passuploadSignature) →assetId. -
store.set_artwithgameId,slot,sources: [{"assetId": "<assetId>"}]and afocalPoint. - Screenshots are real gameplay, never generated:
summer_capture_gameplay(no editor needed),summer_screenshotwithtarget: "game"while the editor plays the game, or ask the owner. Desktop 4-6, mobile 3-5. - No text, logo or caption in key art, the tall cover or icons. Screenshots show the game as it is played: its own HUD is fine, added captions, logos and overlays are not. At most 20 pictures in total.
- Slot table: Store art.
6. 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.
7. Upload
- With the npm MCP: each export with
summer_publish_build(operationstore.upload_file),gameIdand a newclientVersion(web builds and downloads take theirplatformfrom the export). The first call checks the game and returns what it will upload. Show that to the owner, and call again withconfirm: trueonly after they approve this exact file and version. - Without the npm MCP:
store.upload_begin(kind:bundle,webordownload),store.upload_sign_parts, PUT each part,store.upload_complete, thensummer_jobs_wait. See Upload and publish. - On a game that is already live, a web build or download is finished by the owner in Studio.
-
summer_store_statusshows each uploadready. Onfailed, fix and upload a new version.
8. Check
-
summer_store_get_listing: the checklist has nothing missing. - Optional:
store.preview_linkand show the owner.
9. Go live
- Price: the store page keeps its price. To set the price the owner asked for, use
pricing.set_base. -
summer_go_livewithgameIdand thepublicationIdfromsummer_publish_build. It answers the plan: what goes live. - Show the plan to the owner and ask. Only after they say yes, call
summer_go_liveagain withconfirm: true. -
needs_permission: Publish is off for agents on this account. Ask the owner to click Publish in Studio.
After going live
- The game is live as soon as Summer’s automatic checks pass. There is no review: never tell the owner to wait for one.
-
waiting: callsummer_go_liveagain to keep watching. WithwaitingOn: "summer", every check passed and Summer is finishing the launch. - A failed check: it names the check and its fix. Fix it, upload a new version and go live again.
-
live: give the owner the page link. Never say the game is live beforesummer_go_liveorsummer_store_statussays so. - Later:
analytics.overviewwithdays: 28for the numbers.
Does this not help you? Reach out on Discord!

