store.publish, one input, one answer. This page says which operation does each publishing job. Every input, answer and example is in the generated Operations reference.
How your agent calls them
- Hosted MCP (
https://mcp.summerengine.com/mcp): the common jobs are their own tools, such assummer_games_list,summer_store_get_listing,summer_store_update_listing,summer_store_statusandsummer_store_publish. Any other operation runs throughsummer_call:{"op": "store.set_art", "input": {...}}.summer_searchfinds an operation from the job in plain words. - npm MCP on your computer: the same operations after
summer login, plus the local ones that touch your disk (export and upload from a file). - 3.x tool names such as
summer_store_submitstill work throughsummer_callfor all of 4.x. See 3.x tool names.
Find the game
A Summer project and its game on Summer Games are separate records.
Store page
Text rules: Store page text. Slot sizes: Store art.
Art
See Make store art with your agent.
Build and upload
Step by step: Upload and publish.
Publish and release
summer_go_live first answers the plan; ask the owner, then call it with confirm: true. The game is live as soon as Summer’s automatic checks pass. An answer needs_approval: give the owner approval.url and wait with summer_jobs_wait. See Approvals.
After launch
More: Use the agent for Grow.
Skills and docs
The hosted MCP also serves skills as prompts and resources:Before sign-in
Beforesummer login, the npm MCP answers cloud operations with the error not_signed_in and one next step: run npx -y summer-engine login. The hosted MCP asks you to sign in when you connect it.
Does this not help you? Reach out on Discord!

