The Phaser Game Agent lets you build Phaser games from your own coding agent — Claude Code, VS Code (Copilot), Codex, Cursor, Gemini CLI, and any other MCP-compatible client — running against a private cloud workspace tied to your Phaser account. Your subscription drives the model; your Phaser account owns the workspace and the games it builds.
The @phaserjs/game-agent CLI is the
one-command installer that wires your editor up to it.
npx @phaserjs/game-agent| Page | What's in it |
|---|---|
| Getting started | Install, sign in, verify, and build your first game. |
| How it works | The moving parts — MCP, the two transports, auth, and what gets written where. |
| CLI reference | Every command, flag, and environment variable. |
| Connecting your editor | Per-editor setup: Claude Code, VS Code, Codex, Cursor, Gemini CLI, Antigravity, Qoder, Windsurf. |
| Connecting any other client (manual) | Wire up any MCP client we don't list yet, by hand. |
| Troubleshooting | Tools not showing up, 401s, restarts, credits, and the usual gotchas. |
- Run
npx @phaserjs/game-agent— it detects your installed editors, lets you pick, signs you in via the browser, and writes each one's MCP config. - Restart the editor.
- Ask your agent: "Check my Phaser Game Agent account" — it should greet you by name and show your credit balance. That confirms it's connected and authenticated.
- Then: "use the Phaser Game Agent — open a project and build me a Breakout clone, then preview it."
Everything after that is just talking to your agent.