mcp-memory-service vs home-memory
mcp-memory-service: MCP Memory Service prevents AI assistants from losing context across sessions by automatically capturing project architecture, decisions, and code patterns. This ensures your AI always remembers essential information, eliminating the need for repetitive re-explanation and saving valuable development time.; home-memory: Home Memory is an MCP server that gives your AI assistant structured, persistent knowledge about your home. It turns natural conversation into living, queryable documentation of your home and everything in it. You can document what exists, plan what's coming, and keep track of what's been removed.
TL;DR
- You use Claude Code, Claude Desktop, Cursor, VS Code or another MCP client and want chat sessions to stop starting from zero.
- You want a choice of storage: local SQLite, Cloudflare for multi-device sync, or a hybrid.
- You need team features: the README lists OAuth, a dashboard and document ingestion.
- Your problem is codebase navigation rather than conversation memory; a code-graph tool or a project scaffold fits better.
- You handle sensitive material and cannot put it in a persistent store, especially with cloud sync.
- You want a short README to start from: it mixes release notes with documentation.
Record and query home devices and appliances
Side-by-Side Comparison
mcp-memory-servicehome-memoryFeatures
mcp-memory-servicehome-memoryUse Cases
mcp-memory-servicehome-memoryBest For
mcp-memory-servicehome-memoryFAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.