Need the client configs?
Use the dedicated MCP setup guide for local Claude, Codex, and VS Code integration.
Open MCP setupFAQ
DreamCleanr FAQ
These answers stay grounded in what ships today: local cleanup, receipts, MCP, scheduling, and protected AI state. Future detector families stay labeled as coming next.
What does DreamCleanr clean today?
DreamCleanr currently focuses on Docker-aware cleanup, safe regenerable cache noise, stale helper and probe residue, receipts, scheduling, and preview-first MCP integration.
Does the browser demo scan my files?
No. The homepage demo is a sample flow. Real scans happen locally after install through the CLI or the local MCP server.
Does DreamCleanr auto-delete Claude VM or Docker.raw?
No. DreamCleanr protects the Claude VM bundle, Docker raw VM storage, and protected Claude and Codex support roots by default.
What is still coming next?
Python, Node, Hugging Face, Ollama, and LM Studio detector support is still coming next. The current product exposes visibility for those surfaces, but it does not market guided cleanup for them as already shipped.
How does MCP integration work?
DreamCleanr runs as a local MCP server through python3 -m dreamcleanr.mcp_server and publishes copy-pasteable configs for Claude, Codex, and VS Code.
What is the pricing direction?
Community stays free. Pro remains a later one-time premium macOS shell, and Team remains a later pilot. There is no live subscription checkout in the current product.
Need a cleaner comparison?
Use the grounded comparison page when you want to understand where DreamCleanr fits against broader consumer cleanup tools.
See the comparison