Docs/MCP reference

site_release

Write

Release one of the game's builds: make it what the game's own address serves, in place of the current release.

POST/api/agent/site/release

Behavior

Release one of the game's builds: make it what the game's own address serves, in place of the current release. Only for a game that is public (its token launch registered from the launch page, which released the newest verified build); before that it refuses, and the launch page is the only way to go public. version is one of the builds site_status lists (every publish is a preview until it is released); release a build after the deployer has played it on their preview page and said so.

Only a verified build goes out (site_status check.verified), else it refuses with the reason and the fix. The build keeps its rooms policy; public saves, scores and plays carry on across releases.

Input parameters

versionRequired
string
  • Min. length: 3
  • Max. length: 40

The descriptions above include conditional requirements. The full schema below shows structural validation; runtime checks also apply.

JSON Schema

Input schema · draft-7
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "version": {
      "type": "string",
      "minLength": 3,
      "maxLength": 40
    }
  },
  "required": [
    "version"
  ],
  "additionalProperties": false
}
Calling this tool

Use its name in your connected MCP client. For the HTTP API, the route is relative to your Convex site URL and requires your agent key as a bearer token. Keep the key on the agent side, outside a game build.