Skip to main content
Draft. Summer Apps is in a closed test. This page goes live after the end-to-end test on production.

​
First: does Summer already do it?

An app is something your team has to keep. Your agent first checks whether Summer already does the job: Studio features (the asset library with collections and groups, Pick one and sound choices, Grow dashboards, Team) and the Summer MCP tools. If Summer does it, the agent uses that and tells you where it is. It builds an app only when the need is real and missing, or as a Scratch throwaway that it calls a throwaway and archives with summer_app_update when you are done with it. When something is missing, it reports it to Summer with summer_app_report_gap.

​
Before you start

You need:
  • A Summer account, signed in to Summer Studio in your browser or in Summer Engine.
  • An agent with the Summer Engine MCP: the summer-engine npm MCP on your computer or the hosted MCP at https://mcp.summerengine.com/mcp. See Connect your agent.
  • Or no agent of your own: describe the tool to Summer in Studio chat. Build a new app in Studio > Apps opens it.

​
1. Ask for the tool

Open Summer Studio, then ask your agent (or paste the same text into Studio chat):

Loot table. A shared table of your items with DPS, kept in Summer.

​
2. What your agent does

1

Reads the guide

summer_app_guide returns the build loop, the SDK, the manifest, the UI kit, the design rules and worked examples.
2

Creates the app

summer_app_create makes a Scratch app in your workspace. Your open Studio tab moves to it with the notice “Your agent built Loot table”.
3

Writes the files

An index.html, its JavaScript, and a manifest that declares what the app may do. Here: shared data (data), with an items collection.
4

Publishes

summer_app_publish uploads the files as version 1. Your tab shows the files arriving, then starts the app.
5

Seeds the data

summer_app_data writes your items into the app’s items collection, as the team’s starter data.
6

Looks at it

summer_app_screenshot renders the app with your data and reports errors. The agent fixes them and publishes again until the app is clean in light, dark and at phone width.
7

Listens

summer_app_events waits for what you do in the app and for errors, so the agent can react.

​
3. Use it with your team

  • Everyone in the workspace can open it from Studio > Apps. Edits show up for everyone, live.
  • Choose Keep in the app’s menu, so it does not expire with the Scratch apps. Your agent can do it too: summer_app_update with status: "kept".
  • Choose Pin to sidebar to keep it one click away.

​
4. Change it

Ask again, or choose Edit with agent on the app page to change it in Studio chat. Your agent reads the current files with summer_app_get, changes them and publishes version 2. The open app reloads on the new version. Versions on the app page lists every version; Make live goes back to one.

Change an app. Your agent edits the app and publishes a new version.

​
5. Let your agent use the app’s data

Your agent does not need the app open to read or change its data:

Data as API. Your agent edits the app's shared data; everyone sees it live.

More in Agents and apps.

​
If something goes wrong