Another week, another agent memory system that is about the same as grep in a memory/ directory.
Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5
11–20 of 47 posts
Re: Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5
#12[flagged]
Re: Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5
#13How is this any different from all the other Memory stuff we have? mem0 etc etc that do the same thing?
Re: Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5
#14did you test if that actually outperforms local claude code memory by any metric?
that's a good idea. how might you test this? could also include a codex memory test.
I'm guessing having a portable memory that's comparable with first party memory is the goal.
Re: Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5
#15Cool idea. Why is this beneficial over just using markdown files and allowing agents to grep for whatever they need? I've tried various MCP things in the past and I've found they tend to slow down the agent and waste tokens more than they end up helping, but a better memory system is 100% needed for agents.
for one, the mcp-server architecture makes it usable from claude.ai and other surfaces where you have mcp but no filesystem. there are claude-specific workarounds (workspaces) but you lose portability across systems.
Re: Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5
#16How is this any different from all the other Memory stuff we have? mem0 etc etc that do the same thing?
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.
[0]: https://setoku.com
Re: Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5
#17How is this different from what's built into Claude?
Re: Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5
#18Cool idea. Why is this beneficial over just using markdown files and allowing agents to grep for whatever they need? I've tried various MCP things in the past and I've found they tend to slow down the agent and waste tokens more than they end up helping, but a better memory system is 100% needed for agents.
for one, the mcp-server architecture makes it usable from claude.ai and other surfaces where you have mcp but no filesystem. there are claude-specific workarounds (workspaces) but you lose portability across systems.
Hmm, ok. I guess I rarely use the web interface and everything that I have agents record as "memory" in markdown is always accessible locally. If I'm accessing something remotely, I use the ChatGPT app with remote which connects directly to the host computer.
Re: Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5
#19Cool idea. Why is this beneficial over just using markdown files and allowing agents to grep for whatever they need? I've tried various MCP things in the past and I've found they tend to slow down the agent and waste tokens more than they end up helping, but a better memory system is 100% needed for agents.
im asking the same thing myself for personal projects seems markdown files is best.
i can see for public facing deployments agent memory like this could result in faster roundtrips.
Re: Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5
#20For 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)