looping.gg

DocsBuild on Looping

Getting started

Take a browser game from a local build to a playable preview and token launch.

Connect your agentUpload an existing build

Publish your first game

Looping hosts your finished browser game at <slug>.looping.gg. Build with your own tools, upload a private preview, then launch its token from your account.

  1. Connect and select a project

    Add the Looping MCP to your agent. Confirm your account with looping_whoami, then create or select a project.

  2. Build and upload

    Compile your game locally. Upload the finished folder or ZIP on the create page. Add the Game SDK for saves, rooms and purchases.

  3. Play your private preview

    Check the build report and play it yourself. project_status reports the build check, listing and next step. Fill in the title, cover and controls.

  4. Launch from your account

    project_launch returns your launch page. Choose the token settings and sign in your own wallet. The registered launch releases the verified build.

Already working with an agent?

After connecting, say “Deploy this game to Looping”. It reads the deploy workflow and guides the project to the launch hand-off.

Choose a guide

Upload and publishPrepare a web build, check its private preview and release updates.Game SDKConnect your game to player identity, saves, rooms, scores and purchases.Multiplayer roomsChoose a room model, configure it and connect players through the SDK.Players and savesKeep player progress across sessions, handle conflicts and submit scores.In-game purchasesSet up a catalog and let the platform handle checkout and verified ownership.MCP tool referenceBrowse the tools, HTTP routes and input schemas served by the Looping MCP.

Platform boundaries

Projects, games and series
Organize multiple games and series under one project in Profile → Projects. Each game keeps its address, saves and token. MCP project IDs select an individual game or series; grouping does not expand an agent key’s access.
Your build tools
Looping hosts the output. Your own machine and editor compile the game; there is no hosted build server.
Game and wallet
Games run in an isolated frame. The platform handles sign-in, wallets and checkout; your game receives player identity and purchase results.
Token launch
Token settings and signing stay on the launch page. No MCP tool launches a token or accepts a private key or seed phrase.

The SDK, Unity package and MCP use the Looping Platform License: use them to build and run games on Looping, and only there. Your own game stays yours.