Claude Code Game Studios vs DOOM MCP

Claude Code Game Studios is a scaffold that transforms a Claude Code session into a structured 49-agent game development organization. It organizes agents into tiered hierarchies — Studio Directors at the top, Department Leads in the middle, and domain Specialists at the bottom — with 72 slash command workflows covering everything from game design documentation to engine-specific implementation. Engine-specific agent profiles are included for Godot 4, Unity, and Unreal Engine 5, each with knowledge of platform conventions, shader languages, and asset pipelines. Automated commit hooks act as quality gates, and agents use a propose-before-act pattern that routes major decisions through human approval checkpoints before any code is written. The project gained 828 stars in a single day, suggesting real demand for structured multi-agent game dev beyond the 'one agent, one problem' paradigm. Whether or not 49 agents is the right number, the organizational design — with roles like Narrative Designer, VFX Specialist, and QA Lead each as distinct agent contexts — is a serious attempt at mapping software studio org structure onto LLM workflows.

Chris Nager built a fully playable DOOM that runs as an MCP (Model Context Protocol) app, rendering inline inside Claude and ChatGPT without a separate browser tab. The architecture uses two MCP tools — create_doom_session for inline-capable hosts and get_doom_launch_url as a browser fallback — combined with cloudflare/doom-wasm for the game runtime and a signed token system that maintains session state across both surfaces. The result is the same session whether you're playing inline or in a tab. The key technical challenge was avoiding iframe and CSP (Content Security Policy) issues. Rather than embedding a browser page inside the MCP iframe, the DOOM canvas runs directly inside the host's iframe — a subtle but critical distinction that resolved a class of rendering and input-handling bugs. The final implementation is intentionally stripped down: no save/load, no persistence adapters, just stable playable DOOM. Beyond the novelty, this project is a concrete demonstration that MCP apps are interactive surfaces, not just tool-calling JSON endpoints. The progressive enhancement pattern — same signed-token foundation serving both inline and browser modes — is a reusable architecture for any game or interactive experience that wants to live inside an AI assistant. Nager open-sourced the implementation and the blog post is a detailed technical breakdown.