Skip to main content
For AI agents. Follow it from top to bottom. Each step names the operation and what must be true before you go on. Fetch this page as Markdown: 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_whoami answers with the owner’s account.
  • summer_games_list returns 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, then projects.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-analytics skill. Fire and forget, no personal data. See Analytics in Grow.

3. The store game

  • summer_games_list. If the game is there, use its gameId.
  • Otherwise games.create with title and the listing targets from this table.
  • summer_store_get_listing with gameId: 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 doctor warns when it is older; summer install --yes updates it.
  • Web or download: summer_export_templates list, then install what is missing.
  • summer_export_game with the targets from 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_search with scope: "mine", then scope: "library".
  • If nothing fits, read the plan’s saved direction (plans.directions with planId) and make it: summer_assets_generate_image with the slot’s aspectRatio, then summer_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 (pass uploadSignature) → assetId.
  • store.set_art with gameId, slot, sources: [{"assetId": "<assetId>"}] and a focalPoint.
  • Screenshots are real gameplay, never generated: summer_capture_gameplay (no editor needed), summer_screenshot with target: "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: true if it fits 120-170, else its own tagline and description;
    • contentRating and contentDescriptors.
  • 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 (operation store.upload_file), gameId and a new clientVersion (web builds and downloads take their platform from the export). The first call checks the game and returns what it will upload. Show that to the owner, and call again with confirm: true only after they approve this exact file and version.
  • Without the npm MCP: store.upload_begin (kind: bundle, web or download), store.upload_sign_parts, PUT each part, store.upload_complete, then summer_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_status shows each upload ready. On failed, fix and upload a new version.

8. Check

  • summer_store_get_listing: the checklist has nothing missing.
  • Optional: store.preview_link and 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_live with gameId and the publicationId from summer_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_live again with confirm: 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: call summer_go_live again to keep watching. With waitingOn: "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 before summer_go_live or summer_store_status says so.
  • Later: analytics.overview with days: 28 for the numbers.

Does this not help you? Reach out on Discord!