https://mcp.summerengine.com/mcp; the summer-engine npm MCP on your computer loads the same tools after summer login --store and adds the local ones that touch your disk. Setup: Connect your agent.
The full list of local engine tools is on MCP tools reference. This page covers only publishing.
Projects
summer_list_projects
Hosted. Your Summer Studio projects, newest first: id, name, kind, last edit, share state.summer_get_project
Hosted. One project: name, kind, its board id, the idea it was made from, share state.Store page
summer_store_list_games
Hosted. Your games on the Summer Games store: game id, name, status, platforms. No inputs.summer_store_create_game
Hosted. A new store game with its first draft. Nothing is published.summer_store_get_listing
Hosted. The store page as the store will show it: review state, platforms and stores, text per store, art per slot, price, builds, the publish checklist, and owner approvals with their links.summer_store_update_listing
Hosted. Edit the draft. Omitted fields keep their value. Saving never submits.summer_store_set_art
Hosted. Put pictures into one art slot. Each picture is checked against the slot’s shape and size before upload.summer_store_preview_link
Hosted. A private link to the saved draft on summer.games. Hidden from search; Buy and Play do nothing.Build upload
Store bundles for the Summer Games apps. The localsummer_publish_build does all four hosted steps for you.
summer_build_begin_upload
Hosted. Start an upload. ReturnspublicationId and a plan of 64 MiB parts. Calling again for the same file resumes.
summer_build_sign_parts
Hosted. Upload URLs for parts, each bound to the part’s SHA-256. Send every returned header with the PUT. Sign again for any part that failed.summer_build_complete_upload
Hosted. After every part is PUT: Summer seals the file, makes the build and checks it on each platform. Call again with the same inputs untilready or failed. Nothing goes live.
summer_build_status
Hosted. Builds of a game, or one: version, platforms, state (uploading, processing, checking, ready, failed) and what to do next.
Web builds and downloads
Store versions:web (played on summer.games), macos-universal, windows-x64, linux-x64 (downloaded).
summer_store_version_begin_upload
Hosted. ReturnsversionId and the part plan.
summer_store_version_sign_parts
Hosted. Upload URLs for part numbers. Inputs:gameId, versionId, partNumbers.
summer_store_version_complete
Hosted. Summer checks the file and marks itready or rejected. On a live game only the owner can finish one, because it goes live at once. Inputs: gameId, versionId.
summer_store_version_status
Hosted. Web builds and downloads, or one: platform, status (awaiting_upload, processing, ready, rejected) and the parts already stored. Inputs: gameId, optional versionId.
Submit
summer_store_submit
Hosted. Ask the owner to publish. It never publishes: it returnsawaiting_owner_approval and an approvalUrl for the owner.
summer_store_cancel_submission
Hosted. Withdraw a waiting approval so its link stops working. Inputs:gameId, approvalId.
summer_build_release
Hosted. After the owner approved and Summer’s review passed: release the approved store bundle to players on every platform it passed its checks for. Works only for the exact build the owner approved; anything else is the owner’s click in Studio. Web builds and downloads need no release: they play once the page is live.current (already live), waiting (with the reason) or the release state.
Grow
summer_grow_overview
Hosted, read-only. Players, new players, sessions, play time, day-7 retention, peak players and Sparks earned, for all your games or one.sample: true in the answer means sample data.
Art and assets
summer_upload_image_begin
Hosted. Start uploading a PNG, JPEG or WebP from your disk (at most 32 MB) into your Summer assets, for example store art you cropped. No inputs. ReturnsuploadUrl, the fields to send and a curl example: POST the file as multipart/form-data with every field plus file=@<path>.
summer_upload_image_complete
Hosted. Finish the upload. Returns theassetId for summer_store_set_art.
Other art tools
These tools already exist. They are listed here because publishing uses them.
See Make store art with your agent.
Local tools
summer_export_game
Local. Export with the installed Summer Engine, without a window.summer_export_templates
Local. List and install export templates from Summer’s CDN, SHA-256 checked.summer_publish_build
Local. Upload a store bundle, web build or download from disk, resumable. The first call previews;confirm: true uploads.
Skills and docs
The hosted MCP also serves skills as prompts and resources:Before sign-in
Withoutsummer login --store, the npm MCP shows one tool, summer_store_tools, that says how to sign in. After sign-in the hosted tools load on their own.
Deprecated
summer_creator_publish, summer_creator_releases and summer publish sent a .pck to an older creator API. Use summer_export_game, then summer_publish_build.
Does this not help you? Reach out on Discord!

