DOOM MCP vs Utilyze

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.

Utilyze is an open-source GPU monitoring tool that measures actual compute efficiency — the percentage of theoretical maximum floating-point throughput and memory bandwidth your workload is achieving. The core problem: standard GPU dashboards can read 100% utilization while your actual compute SOL (Speed of Light) percentage sits at 1%, creating dangerous false confidence. The tool tracks three metrics in real time: Compute SOL% (actual FLOPS vs theoretical max), Memory SOL% (achieved bandwidth vs peak capacity), and Attainable SOL% (the realistic ceiling given your workload's arithmetic intensity). This lets ML engineers immediately identify whether they're compute-bound or memory-bandwidth-bound and pull the right optimization levers. Built by Systalyze and released under Apache 2.0, Utilyze currently targets NVIDIA hardware with AMD MI300X/MI325X support planned. For any team spending real money on GPU compute for AI training or inference, this kind of visibility can cut cloud costs significantly — and it runs with negligible overhead, meaning you can monitor in production without affecting workload performance.