AI tool comparison
claude-mem vs DOOM MCP
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
claude-mem
Persistent cross-session memory for Claude Code — 10x cheaper context
75%
Panel ship
—
Community
Paid
Entry
Claude-mem is a plugin that automatically captures and compresses coding session context, then intelligently reinjects relevant memory into future Claude Code sessions. With 67K GitHub stars, it has rapidly become one of the most widely-adopted quality-of-life improvements for developers using Claude Code daily. The system hooks into five lifecycle events — SessionStart, UserPromptSubmit, PostToolUse, Stop, and SessionEnd — to capture observations and store them in an SQLite database with FTS5 full-text search, backed by a Chroma vector database for semantic hybrid retrieval. A real-time web viewer at localhost:37777 shows the memory stream live. Progressive disclosure layers memory retrieval with token cost visibility, and a "<private>" tag excludes sensitive content from storage. Beyond Claude Code, claude-mem works with Gemini CLI, OpenCode, and OpenClaw gateways, making it gateway-agnostic persistent memory. The AGPL-3.0 license with a PolyForm Noncommercial exception on the ragtime/ module means it's free for personal use but requires source-sharing for networked commercial deployments.
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.
Reviewer scorecard
“If you're using Claude Code heavily, this is table stakes. The FTS5 + vector hybrid search means you stop re-explaining your codebase conventions every session, and the 10x token savings claim holds up in practice. The lifecycle hook architecture is clean and non-intrusive.”
“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 AGPL license with a PolyForm Noncommercial carve-out creates real ambiguity for commercial teams. And piping your entire coding session history into a local SQLite database raises legitimate data security concerns for enterprise work. Test thoroughly before using on proprietary code.”
“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.”
“This is what personalized AI looks like at the tooling layer — not a vendor feature, but community infrastructure that makes agents progressively smarter about your specific context. The gateway-agnostic design means this pattern will outlast any single coding agent product.”
“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.”
“For anyone using Claude Code to manage creative projects, writing systems, or content pipelines, the cross-session continuity transforms the experience from stateless assistant to genuine collaborator. The web viewer UI is a nice touch for understanding what your agent actually remembers.”
“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.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.