Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5
46 points by pcbmaker20 5 hours ago | 22 comments
ksajadi 2 hours ago
For those looking for similar tools, there is also https://markbase.cloud/ as a hosted service. (Disclaimer: we built it for internal use first and would like to open source with the community help as we don’t have much experience in OSS maintenance)
replyrcarmo 4 hours ago
Nice to see more OKF-based approaches. My entry in this field is https://rcarmo.github.io/projects/memento/, which I’ve been running for a few months now.
replyejp 4 hours ago
Since you built something on OKF, how would you contrast it with knowledge graph implementations? How do you manage the ontology of what to keep knowledge about? Any cases where traversal would have helped?
replydofm 4 hours ago
Please excuse my noob-ish, naïve question, but to what extent is the business of getting the LLM to actually consult memory a model-dependent thing? Do you have to introduce the tool and guide models with different language for different model families?
replyLooking at your tool descriptions (as wit the ones on the original post) I wonder if this something perhaps only current frontier models will do, but the systems themselves seem like they'd be even more useful for open weights models with shorter working contexts.
esafak 4 hours ago
I have seen the value of recording past sessions but I am more skeptical of the value in recording facts, which may soon become stale, about a constantly changing code base. Got benchmarks?
replysho 4 hours ago
Well, do you see the value of writing notes for yourself occasionally, even though they might soon become stale in your constantly changing environment? Yes, right?
replySame principle. It's a good idea to have a schedule to clean them up periodically - an idea you can also put into a note.
healthycoder 3 hours ago
How is this any different from all the other Memory stuff we have? mem0 etc etc that do the same thing?
replyrgbrgb 2 hours ago
agree there are a lot of these but they're all pretty simple (including mine [0]) so I think building your own and playing around with architecture is useful and fun.
reply[0]: https://setoku.com
FitchApps 4 hours ago
Looks very interesting. Can you explain for noobs why using Google's OKF format and not plain MD files?
replyclemens1010 4 hours ago
did you test if that actually outperforms local claude code memory by any metric?
replybearjaws 3 hours ago
Another week, another agent memory system that is about the same as grep in a memory/ directory.
replymyshapeprotocol 3 hours ago
Using SQLite FTS5 for fast agent memory is such a pragmatic architectural choice. Great Show HN project.
reply
Having an inverted index (as with FTS5) is useful in that, for a basic single-term lookup, you reduce a sequential scan, O(N), down to O(log N). For small N, the performance difference might not be meaningful. Performance gap widens with more sophisticated queries (boolean operators, ranking, etc).
i can see for public facing deployments agent memory like this could result in faster roundtrips.