Skip to main content
Export, upload builds, write the store page and ask the owner to publish. 25 tools. What each column means, and how to connect: MCP tools reference.
Generated from the tools’ own definitions: the summer-engine npm package 3.3.0 (its MCP server’s tools/list, library/tools/*/resource.yaml and registry/generated/index.json in SummerEngine/summer) and the hosted Summer Engine MCP (src/lib/mcp/hosted at commit 8c4351ee30). If something here is wrong, the tool definition is wrong.

summer_build_begin_upload

On the hosted MCP. Start uploading an exported game build (the summer.games .zip bundle or one .pck) to a store game: the same build-publication steps as Studio upload. Returns publicationId and the part plan (64 MiB parts). Then hash each part, call summer_build_sign_parts, PUT each part to its URL with every returned header, and finish with summer_build_complete_upload. The local summer-engine MCP does all of this from disk (summer_publish_build). Calling again for the same file resumes. Inputs:
Output: MCP text content holding JSON; errors set isError. From the tool’s own description: Returns publicationId and the part plan (64 MiB parts).
Example call

summer_build_complete_upload

On the hosted MCP. Finish a build upload after every part is PUT: Summer seals it, makes the Build and names its client pack, then checks it on each target platform. Safe to call again with the same arguments until it reports ready or failed. A store page that has not passed review keeps the build as a preview; nothing goes live here. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_build_release

On the hosted MCP. After the owner approved publishing and Summer staff approved the game, release the approved bundle build to players on every platform it passed its checks for. Works only for the exact build the owner approved (summer_store_submit); anything else is the owner’s click in Studio. Web builds and downloads need no release: they play as soon as the store page is live. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_build_sign_parts

On the hosted MCP. Get upload URLs for parts of a build started with summer_build_begin_upload. Each URL is bound to its part’s SHA-256; send every returned header with the PUT. Sign again for any part that failed or expired: re-sending a part is safe. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_build_status

On the hosted MCP. Read uploaded builds of a store game (or one, by publicationId): version, targets, state (uploading, processing, checking, ready, failed) and what to do next. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_creator_config

On the local MCP (summer-engine npm). Read or update the shared non-secret ~/.summer configuration used by the CLI and this MCP. Mutations require confirm=true. Tokens are never returned or accepted by this tool. Use when:
  • inspecting or changing shared CLI and MCP configuration values
  • “which creator project id / channel is this CLI pointed at?”
  • switching the default publish channel
Do not use when:
  • reading or setting auth tokens — they never pass through this tool; use summer login / logout
Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_creator_publish

On the local MCP (summer-engine npm). Deprecated: use summer_export_game, then summer_publish_build, which upload the summer.games .zip to the game’s store listing. This old path publishes a .pck to the legacy Summercraft creator API with a separate sc_ token and will be removed. First call with confirm=false and present the returned project, version, digest, size, artifact path, channel, and notes; set confirm only after the user approves that exact target. The server independently verifies token scope, ownership, bytes, and review state. Use when:
  • releasing a user-approved build to a Summercraft channel
  • “ship this exported build to the live channel”
  • “release version 1.2.0 of my game”
Do not use when:
  • uploading to summer.games — summer_export_game, then summer_publish_build
  • the user has not approved the exact version, digest, and channel
  • the game is not exported yet — export the .pck first (skill/export-and-ship)
Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_creator_releases

On the local MCP (summer-engine npm). List real creator-owned releases from the versioned Summer Platform creator API. The server independently verifies the exact publish scope and project ownership. Use when:
  • reviewing which versions of a project are live per channel
  • “what version is live right now?”
  • “did the publish go through?” — confirming a release landed
Do not use when: Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_export_game

On the local MCP (summer-engine npm). Export the game in the exact file the Summer Games store takes, with the installed Summer Engine headless (no window). format “bundle” (default): the summer.games .zip the Summer apps run on iPhone, Android, macOS and Windows; targets picks the platforms (a game without a server: ios and android only); upload it with summer_publish_build. format “download” with one target: web (an HTML5 .zip on Summer’s WebGPU Forward+ web template, played on summer.games), macos (.app zip, macos-universal) or windows (.exe zip, windows-x64); these need the export template from summer_export_templates and are uploaded as store versions. Works without the editor running. Returns path, sha256, size, the manifest or store platform, and warnings. Use when:
  • “export my game for summer.games”
  • “make a build I can upload to my store page”
  • “export my game for iPhone and Android on Summer Games”
  • “make a web build of my game for summer.games”
  • “export a Mac or Windows download for my store page”
  • preparing the bundle that summer_publish_build uploads
Do not use when:
  • exporting for Steam, itch.io, the App Store, Google Play or other stores — skill/export-and-ship
  • the game is still being built; export when the user wants a Build
Inputs:
Output: MCP text content holding JSON; errors set isError. From the tool’s own description: Returns path, sha256, size, the manifest or store platform, and warnings.
Example call

summer_export_templates

On the local MCP (summer-engine npm). List, download and install Summer Engine export templates from Summer’s CDN into the folder the installed engine reads, checking each file’s sha256. Needed only for summer_export_game format “download”: web (Summer’s WebGPU Forward+ template), macos, windows. Store bundles (format “bundle”) need no template. action list shows what is installed and published; action install fetches the platforms asked (default web). Use when:
  • “install the web export template”
  • “summer_export_game says an export template is missing”
  • “which export templates do I have”
  • before a web build or a macOS/Windows download export on a machine whose Summer Engine does not bundle that template
Do not use when:
  • exporting the summer.games store bundle (iPhone, Android, macOS, Windows apps) — it needs no template, tool/export-game
  • exporting for Steam, itch.io or other stores — skill/export-and-ship
Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_get_project

On the hosted MCP. Get one Studio project: name, kind, its board id (summer_board_read), the idea it was made from, share state and address. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_list_projects

On the hosted MCP. List the user’s Summer Studio projects (games), newest first: id, name, kind (create: made in the browser; cloud; desktop), last edit, share state and where it opens. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_publish_build

On the local MCP (summer-engine npm). Upload an export from summer_export_game to the creator’s game on summer.games, through the same store upload Studio uses, straight from disk. A store bundle (format bundle): declare, upload parts, seal, wait until Summer makes the Build, name its client pack, and with publish=true approve it. A web build or native download (format download): upload it as the game’s store version for its platform (web, macos-universal, windows-x64, linux-x64; read from the last export) and wait until Summer has checked it. First call with confirm=false and show the user the returned target; set confirm only after they approve. Needs “summer login —store”. A retry with the same file and clientVersion continues the same upload. Nothing here makes a game live: the owner approves publishing (summer_store_submit). Use when:
  • “upload my game to summer.games”
  • “publish this build to my store page”
  • “put my game online so my friends can play it”
  • uploading the .zip from summer_export_game as a new Build
  • uploading a web build or a macOS or Windows download from summer_export_game format download
Do not use when:
  • the user has not approved the exact game, file, digest, version and publish choice
  • the game is not exported yet — summer_export_game first
  • store page text, images or price — those are edited in Studio
Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_store_cancel_submission

On the hosted MCP. Withdraw a waiting owner approval (from summer_store_submit) so its link no longer works. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_store_create_game

On the hosted MCP. Create a game on the Summer Games store with its first store page draft. Targets decide the store flows: web, macos-universal, windows-x64, linux-x64 open the desktop store; ios, android open the mobile store. Nothing is published. Slot sizes and text rules: read the store-art and store-listing skills (MCP prompts/resources). Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_store_get_listing

On the hosted MCP. Read a game’s store page as the store will show it: review state, targets and store flows, text per flow (desktop, mobile), art per slot, price, uploaded builds, the publish checklist (what is missing), and any owner approvals with their links. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_store_list_games

On the hosted MCP. List the user’s games on the Summer Games store (the creator catalog): game id, name, status and targets. A Studio project and its store game are separate records. Inputs: No inputs.
Output: MCP text content holding JSON; errors set isError.
Example call

On the hosted MCP. Make a private link to the saved store page draft on summer.games (noindex; Buy and Play do nothing) to show it to someone or look at it. Expires after 1h, 1d or 7d. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_store_set_art

On the hosted MCP. Put images into one store art slot from your Summer assets (assetId) or public image URLs. Slots: desktop.keyArt, desktop.screenshots, desktop.icon, desktop.capsuleTall, desktop.capsuleWide, mobile.icon, mobile.tallCover, mobile.keyArt, mobile.screenshots. Each image is checked against the slot’s shape and minimum size before upload (icons 1:1, key art 16:9, tall capsule 3:4, wide capsule 460:215, mobile tall cover 9:16, phone screenshots 16:9 or 9:16); no text in key art, icons, the tall cover or screenshots. Screenshots take a list (mode replace or append); other slots take one image. An empty sources list clears the slot. Generate missing art with summer_generate_image first. Slot sizes and text rules: read the store-art and store-listing skills (MCP prompts/resources). Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_store_submit

On the hosted MCP. Ask the owner to publish the store page draft with a build and price. This never publishes by itself: Summer Games records exactly this version and waits for the owner, signed in to Studio, to click “Approve publishing” at the returned approvalUrl. Give the owner that link. After approval Summer staff review the game; then it can go live. Checks the publish checklist first and lists what is missing. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_store_update_listing

On the hosted MCP. Edit the store page draft: title, targets, desktop text (tagline, description, 3-8 tags), mobile text (its own shorter tagline and description, or mobileSameAsDesktop to copy the desktop text once), release date and content classification. Omitted fields keep their value. A page that was published or sent back starts a new draft; a page in review cannot change. Saving never submits. Slot sizes and text rules: read the store-art and store-listing skills (MCP prompts/resources). Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_store_version_begin_upload

On the hosted MCP. Start uploading a web build or a desktop download to a store game (summer_export_game with format “download” makes these). web: a .zip with index.html at its root (at most 500 MiB, 2000 files), played on summer.games in a frame. macos-universal, windows-x64, linux-x64: the archive players download (at most 20 GiB). Returns versionId and the part plan; then summer_store_version_sign_parts, PUT each part, summer_store_version_complete. The local summer-engine MCP does all of this from disk. Inputs:
Output: MCP text content holding JSON; errors set isError. From the tool’s own description: Returns versionId and the part plan; then summer_store_version_sign_parts, PUT each part, summer_store_version_complete.
Example call

summer_store_version_complete

On the hosted MCP. Finish a store version upload after every part is PUT. Summer checks the file (a web zip needs index.html at its root) and marks it ready or rejected. On a game that is already live, a finished version goes live at once, so Summer Games lets only the owner finish it there. Safe to call again. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_store_version_sign_parts

On the hosted MCP. Get upload URLs for parts of a store version (web build or download). Send every returned header with the PUT. Sign again for any part that failed; summer_store_version_status lists the parts already stored. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_store_version_status

On the hosted MCP. Read a store game’s web builds and downloads (or one, by versionId): platform, status (awaiting_upload, processing, ready, rejected) and, while uploading, the parts already stored. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call