DOOM MCP vs Rova AI

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.

Rova AI is an autonomous testing agent that flips how QA works — instead of writing brittle test scripts, you define what should be true about your product, give it a URL, and Rova navigates, explores, and validates on its own. It's designed for teams that can't keep up with constant UI changes that break traditional automation. Under the hood, Rova uses a planning-execution loop: analyze the product, generate structured test plans (which humans can review and edit), then execute autonomously, logging bugs and generating comprehensive reports. When the UI changes, Rova adapts its paths instead of crashing. It integrates with Jira, Linear, Slack, and GitHub, and can be triggered with @rova directly in tickets — meaning bugs get flagged in the same place engineers already work. In a landscape cluttered with "AI-enhanced" test tools that still require significant scripting, Rova positions itself as a genuinely zero-script option for end-to-end QA. For startups shipping fast without dedicated QA teams, that's a real value prop — and its Product Hunt debut on April 30, 2026 signals growing market appetite for agentic quality assurance.