Not a vector database. MemoryLayer reasons over what it's told, catches contradictions, derives facts you never stated, and checks every claim before your agent repeats it. Local-first, MCP-native. One command and you're live.
No reviews yetBe the first to leave a review for MemoryLayer
Maker
📌
Hey PH! I'm Raaj, the maker of MemoryLayer.
I built this because I kept hitting the same wall: my AI coding agent would answer the same question differently in every session, hallucinate a function signature it had already learned was wrong, or suggest a change without knowing what else it would break. The problem wasn't the model - it was that there was no persistent, reasoning layer between sessions.
Most memory tools are just vector DBs. They find similar text and return it. MemoryLayer does something different: it extracts subject-verb-object triples from everything you tell it, runs them through a biologically inspired reasoning engine that catches contradictions, derives facts you never explicitly stated, and then uses Z3 formal logic to verify claims before repeating them. When it doesn't know, it says so instead of guessing.
It's local-first - your memories never leave your machine. It drops into Claude Code, Cursor, and Windsurf via one MCP config line. No server to run, no account required for the free tier.
The registry at registry.memorylayer.in lets you publish memory packages (.memorypkg files) so teams can share domain knowledge - think npm but for your agent's institutional memory.
I'd love to hear: what's the most painful memory failure you've hit with AI coding tools? That'll help me know what to build next.
Install: npm install -g @raajvamsy/memorylayer && memorylayer setup
Try the live demo: memorylayer.in/arena
Report
Spun it up locally and honestly the contradiction catching caught me off guard, it flagged something I genuinely didn't realize was inconsistent in my own notes. The local-first setup is genuinely one command, which I appreciate.
Report
spun it up locally and the contradiction catching actually works, like I fed it conflicting info on purpose and it flagged it right away. kind of wild that it derives facts too, that part genuinely surprised me.
Report
Caught a contradiction in my test notes I'd missed myself, which was honestly unsettling in the best way. The MCP setup was genuinely one command, no fighting config files.
Report
The local-first, MCP-native stance is genuinely rare in this space, and the contradiction-catching angle is what sold me. Most memory tools just stuff everything into a pile and hope for the best.
Spun it up locally and honestly the contradiction catching caught me off guard, it flagged something I genuinely didn't realize was inconsistent in my own notes. The local-first setup is genuinely one command, which I appreciate.
spun it up locally and the contradiction catching actually works, like I fed it conflicting info on purpose and it flagged it right away. kind of wild that it derives facts too, that part genuinely surprised me.
Caught a contradiction in my test notes I'd missed myself, which was honestly unsettling in the best way. The MCP setup was genuinely one command, no fighting config files.
The local-first, MCP-native stance is genuinely rare in this space, and the contradiction-catching angle is what sold me. Most memory tools just stuff everything into a pile and hope for the best.