VanitasCaesar1/vesta-arcade

Your coding agent can build a game. It can't watch anyone play it.
Vesta is a self-hosted arcade that can. Tell your agent “publish this to Vesta” and get a link anyone can play.
Then get back the crashes, the drop-off and what players said, in a form your agent can fix.
Runs on your own Cloudflare account, on the free plan.
▶ Play: Microservices (exit vim in under a second) · Live arcade
Quick start ·
For agents ·
How it works ·
Architecture ·
Demo game
Play them: Microservices · Hug of Death · Ignore Previous Instructions · Garbage Collector
## Why
Making a browser game with Claude Code, Cursor or Codex takes an afternoon now. What happens next is the hard part. You paste a link somewhere, a few people click it, and you never learn that it crashed on Safari, that half of them quit in the first ten seconds, or that level 3 is impossible.
Vesta closes that loop:
your agent ──publish──▶ playable link ──▶ people play
▲ │
└──── errors, drop-off, comments ◀─────────┘
Publish from the editor. One command, or one MCP tool call from your agent. Every publish is a new version with a changelog.
Feedback an agent can act on. Uncaught errors with stack traces, grouped and counted. How long sessions last. How far players get. What they wrote. One Markdown report, made to be pasted into an agent, or fetched by one.
Yours. It deploys to your Cloudflare account in one command and fits in the free plan. No platform cut, no AI-content policies, no one else's terms.
## Quick start
You need Node 20+ and a free Cloudflare account.
sh
npx vesta-arcade setup # deploys your arcade (~2 minutes, opens a browser to sign in to Cloudflare)
npx vesta-arcade publish # run in any folder with an index.html, or a built dist/
▲ Hug of Death v1 is live (new game)
https://vesta.you.workers.dev/g/hug-of-death
1 files · 31.6 KB · cover: screenshot
Want it on your own domain? npx vesta-arcade setup --domain games.example.com (the domain must be on the same Cloudflare account). If the domain already serves a site, Vesta takes over the pages it knows and passes everything else through to the old site.
That's it. publish finds your build folder (dist/, build/, out/ or the folder itself), uploads it, screenshots the game for a cover image if you have Chrome or Playwright's Chromium, prints a QR code for your phone and saves the game's slug in vesta.json, so the next publish becomes v2.
## For coding agents
Add Vesta as an MCP server, then just ask: “publish this game to Vesta”, and later, “check the Vesta feedback and fix the top error”.
sh
claude mcp add vesta -- npx -y vesta-arcade mcp # Claude Code
For Cursor, Codex, Windsurf, Cline and other MCP clients, add this to their MCP config:
json
{ "mcpServers": { "vesta": { "command": "npx", "args": ["-y", "vesta-arcade", "mcp"] } } }
| Tool | What it does |
| publishgame | Uploads the project (optionally builds it first) and returns the public link |
| getfeedback | Markdown report: errors with stacks, session lengths, milestones, comments, versions |
| listgames | Every game on the arcade, with plays and likes |
| setcover | Sets the cover image used in the arcade and in link previews |
| arcadestatus | Whether an arcade is configured, and where |