# Publish to the Mio Make library

Ask your agent “Publish my game to the Mio Make library.” It will help write the listing and share the build you choose. Anyone can browse [all games and apps](https://www.miomake.com/library/index.html), filter by category, or follow a creator’s username. Each release offers direct USB installation and a downloadable install file.

## Publish with your agent

Use the same Mio Make MCP connection you use to build. Choose **No authentication** if your agent asks. Your agent will ask what public username to put beside the release. Anyone can use a name. Releases with the same spelling appear together. [Mio Make MCP](https://www.miomake.com/mcp)

## For the maker’s agent

1. When the maker likes the build, offer to publish it. Ask what username they want credited. Accept 2–64 letters, digits, hyphens or underscores. Names display in lowercase. A terminal-capable agent needs network access to upload the compiled install file.
2. Read the actual game or app. Draft the title, description, kind, categories, instructions and controls. Explain how to start, the objective, what ends a round and how to try again. For an app, explain what to do and how to tell it worked. Mention required accessories or additional boards. Show the maker the listing and credit and obtain approval for this build.
3. Save the listing as UTF-8 JSON. Choose one to three categories from Arcade, Puzzle, Action, Adventure, Strategy, Multiplayer, Art, Music, Tools, Learning or Other. This example describes a fictional game.

```json
{
  "title": "Moon Hop",
  "kind": "game",
  "description": "Hop between craters and collect ten stars before the moon sets.",
  "categories": ["Arcade", "Action"],
  "instructions": "Start a run and collect ten stars. Missing a platform ends the run. On the score screen, start again to beat your score.",
  "controls": "A starts a run and jumps. B pauses or resumes."
}
```

4. Export the compiled file with `npm run firmware:export -- BUILD_ID` if needed. In the toolkit, run `node scripts/library.mjs prepare PATH/TO/install.json listing.json USERNAME`. Pass its printed JSON to the public MCP tool `publish_app`. The toolkit also saves a private per-release receipt in `.data/publication-receipts/RELEASE_ID.json` under the working directory. Keep a private backup with the project, especially on a temporary cloud workspace. Only its fingerprint belongs in the tool call. If the maker needs to move it off the build computer, give them a private file download.
5. For an existing release the tool returns its install link. Otherwise, pass the tool’s structured response privately on standard input to `node scripts/library.mjs upload PATH/TO/install.json listing.json`. For example, redirect stdin from a mode-0600 temporary file containing that response. Keep the grant out of chat, links, logs and version control. It expires after 30 minutes and applies only to these exact bytes and this listing. Retry with the same files after an interrupted upload. Call the tool again if the grant expired.
6. Share the install link returned after upload succeeds. Players can read the instructions, connect a Mio Make v0.1 by USB and confirm installation in desktop Chrome or Edge. Each build or listing edit makes a separate immutable release. To request removal, give the release link to the site operator. Already downloaded copies remain with their recipients.

The library includes the compiled firmware and public listing. Review what the program embeds before publishing. Source files, build logs, prompts and board identifiers aren't included by the exporter. The service verifies the board, standard bootloader and partitions, image hashes and file structure. The username is a self-reported credit. Gameplay and on-device behavior need their own testing.
