With an AI agent

Everything about a game is text, and every command an agent needs is in the CLI, so an agent can build a whole game from these docs while you watch it land in Eggox.

The loop

1. eggox pull "My Game" gives the agent the folder.
2. It reads the folder format, the bricks and the scripting API. Each page is also plain markdown: add .md to its address, or fetch /llms.txt for the list.
3. It writes files, runs eggox check, and fixes what the check names: compile errors by line (things/Guardian.lua:12: syntax error) and the playability warnings (no SPAWN, rounds with no WINNER) that would stop the publish later.
4. eggox push makes the game the draft. You open Eggox and play it.
5. eggox publish is yours. An agent can push all day; only a person ships.

MCP

The CLI is also an MCP server, so an agent with MCP support gets the same commands as tools without shelling out:

{ "mcpServers": { "eggox": { "command": "eggox", "args": ["mcp"] } } }

The tools are eggox_games, eggox_pull, eggox_check, eggox_push, eggox_playtest, eggox_logs, eggox_bag, eggox_stock, eggox_stock_add and eggox_docs. There is no game-publish tool.

eggox_playtest is how an agent sees its game run: push, play a scenario headless (click Kettle; key space; wait 2), and read every effect and handler error, step by step, with no browser. eggox_logs reads back the last playtest a human ran in Eggox. See eggox playtest. Every Eggox repository standardizes on AGENTS.md for agent instructions.

On a machine with no browser

eggox login needs a browser once. For a headless machine, log in elsewhere and set EGGOX_TOKEN in the agent's environment; see login.

A good first prompt

> Read the eggox docs for the project format, the bricks and the scripting > API. Pull "My Game". Make a race: a spawn, a finish, rounds of two minutes, > and a sign at the start that explains it. Check until it compiles, push, > and tell me what you changed.

Blueprints use the same login and MCP process. eggox_blueprints lists your items; eggox_blueprint_schema exports the offline frame contract. The eggox_blueprint_init, pull, check, frame, push, and history tools work with files, keeping voxel arrays out of tool replies. Tools never spend Voxels: publishing an iteration costs them, so the user publishes in Eggox. eggox_blueprint_mint strikes the editions of a published iteration (free, once per design, the count is its whole supply) when the user asks. A push can be refused with design_taken when a frame copies somebody else's blueprint exactly. Old games-only logins need eggox login again to approve creator access. See Blueprint files, or eggox docs blueprints.