AI tool comparison
DOOM MCP vs GitNexus
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
DOOM MCP
Play DOOM inline inside Claude or ChatGPT — full game, no browser needed
75%
Panel ship
—
Community
Free
Entry
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.
Developer Tools
GitNexus
Turns any codebase into a queryable knowledge graph with MCP support
75%
Panel ship
—
Community
Free
Entry
GitNexus is a client-side code intelligence engine that indexes any codebase into a knowledge graph — mapping every dependency, call chain, cluster, and execution flow. The result is a semantic map that AI agents can query intelligently rather than reading raw files or relying on fuzzy embeddings. It ships with two interfaces: a CLI that runs an MCP (Model Context Protocol) server for direct integration with Cursor, Claude Code, and other editors, and a browser-based web UI for visual exploration that runs entirely in-browser with WASM. The 16 specialized tools include query, context analysis, impact assessment, change detection, rename coordination, and cross-repo contract matching. Tree-sitter parsing gives it language-aware understanding across any stack, while a registry-based architecture lets one MCP server manage multiple indexed repos. With ~32k GitHub stars and a PolyForm Noncommercial license (free for individuals, enterprise SaaS available), GitNexus hits a sweet spot: it runs locally, code never leaves your machine, and the MCP integration means your AI coding assistant gets precise structural context instead of guessing. The project also auto-generates repo-specific skill files tailored to each codebase's code communities.
Reviewer scorecard
“The signed-token progressive enhancement pattern is the part worth stealing. This is a clean reference architecture for MCP interactive apps, and DOOM just happens to be the demo case.”
“The primitive is clean: Tree-sitter parses your code into an AST, GitNexus lifts that into a graph, and the MCP server exposes 16 typed query tools so your AI editor gets call-chain context instead of hoping embeddings land on the right file. The DX bet — local-first, zero egress, registry-based multi-repo management — is exactly the right place to put the complexity, because the alternative is pasting 3,000 lines into a context window and praying. The moment of truth is `npm run index` followed by wiring the MCP server into Cursor; if that path is clean and the impact-assessment tool actually surfaces the correct transitive dependents on a real-world monorepo, this earns every one of its 32k stars.”
“Fun proof of concept but let's be honest: if your AI assistant is hosting a DOOM session, something has gone wrong with your productivity. The MCP-as-interactive-surface insight is real, but this specific app has no utility.”
“Direct competitors are Sourcegraph's code intelligence layer and whatever OpenAI embeds into its next editor plugin — GitNexus wins on the local-first, no-egress angle, which is a real differentiator for enterprise shops with compliance requirements, not a marketing checkbox. The tool breaks at the scale of a true monorepo with 10+ languages and circular dependency hell, where any static graph starts lying to you about runtime behavior — the claim that Tree-sitter gives 'language-aware understanding across any stack' has limits the landing page doesn't cop to. What kills this in 12 months isn't a competitor — it's Cursor or VS Code shipping a first-party structural context layer baked into the MCP spec, at which point GitNexus needs the enterprise distribution it's already positioned for to survive.”
“Every major compute platform's pivot point is when it runs DOOM. MCP running DOOM means MCP is a real platform now. The implications for interactive AI-embedded experiences are significant.”
“The thesis is falsifiable: within three years, AI coding agents will fail or succeed based on the quality of structural context they receive, and fuzzy vector search over file contents is not sufficient — graph-structured code intelligence becomes load-bearing infrastructure. The dependency is that MCP actually becomes the standard handshake between editors and context providers, which is early but directionally correct given Anthropic's investment in the spec. The second-order effect nobody's talking about: if every agent queries a shared code graph instead of each reading files independently, the graph itself becomes the source of truth for what the codebase *means*, shifting power from the editor vendors to whoever controls the indexing layer — and GitNexus is betting on being that layer with its registry-based multi-repo architecture.”
“As someone who thinks about interactive experiences, the idea of game-like UI living inside an AI context is genuinely exciting. This is a crude ancestor of what interactive AI-native media could become.”
“The buyer for the free tier is obvious — individual developers who care about privacy — but the check-writer for the enterprise SaaS tier is a VP of Engineering who already has Sourcegraph on contract, and GitNexus has no stated sales motion, no documented enterprise pricing, and no clear story for why legal will approve a PolyForm license transition at renewal time. The moat is thin: Tree-sitter is open source, MCP is an open protocol, and the graph indexing logic is the kind of thing a well-funded competitor replicates in a quarter. The business survives only if it converts its 32k GitHub stars into a paid community before the platform players close the gap — right now there's no evidence that flywheel is turning.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.