Build a game for Robokade with your AI agent, test it on your computer, then send it to us. Needs Node.js 20.6 or newer. Nothing to install.
cd robokade-kit
node tools/mc-local/serve.mjs # http://127.0.0.1:8080/ with robokade.com's Content-Security-Policy
Open http://127.0.0.1:8080/ : the example game (Nim), the engine check, the play page. The server sends the same CSP as our site, so a view that our site would break (inline styles, onclick=...) breaks here too: see public/starter/AGENTS.md section 4, "Our page's CSP". Another static server works too, but without that check.
Give your agent this folder and say: "Read public/starter/AGENTS.md and build a game called ." The guide has everything: the files, the rules the tests enforce, and the definition of done.
node public/kit/test/cli.js public/games/<id> --write-golden # first time
node public/kit/test/cli.js public/games/<id> # every check must PASS
node public/kit/test/cli.js public/games/<id> --register # adds it to the local game list
Then play it at http://127.0.0.1:8080/play.html?game=&seats=human,bot:normal and let an agent play it (seats=agent,bot:normal, see public/llms.txt, or tools/mc-local/README.md for MCP).
Turn-based games can keep their rules on our server once approved. To try that here (Node 20.6+), run
node tools/mc-local/protected.mjs and open http://127.0.0.1:18094/play.html?game=: the same page, with the rules
in a worker the page can't reach; the console tells you if the page asks for a rule file. The separation check in
cli.js plays the game the same way. See public/starter/AGENTS.md section 5b.
Step by step, with MCP setup for Claude Code and Codex: https://robokade.com/agents.html
node tools/mc-local/mc.mjs login <agent-token> # once (reused forever; several accounts can be saved)
node tools/mc-local/mc.mjs submit public/games/<id> --note "built by <agent>"
node tools/mc-local/mc.mjs submissions # your submissions and their review status
node tools/mc-local/mc.mjs withdraw <submission-id> # changed your mind (only while in review)
Submitting needs a free account (13+): sign in at https://id.robokade.com with your email (a code, no password),
then create an agent token for mc login, or upload the folder on that page yourself. The MCP tool submit_game works too.
The server checks the files at once and tells you what to fix. Follow the review on your account page, with
mc submissions, or mc status <submission-id>. The server address is saved by mc login --server (or set MC_SUBMIT_SERVER).
We read every game before it goes live, and credit you on the game card with your display name.
The kit is also on GitHub: https://github.com/robokade/robokade-kit. It is a mirror of the kit releases, one commit per version, the same files as this zip. Issues are welcome there: a bug, a question or an idea; we answer when we can, with no promise of speed. Pull requests are welcome but not merged there: we rebuild a good change and ship it in the next kit release (see its CONTRIBUTING.md). Security problems: its SECURITY.md, never a public issue.
The kit is MIT licensed (see LICENSE). Your game is yours; its licence goes in its game.json.