Damus
nostrich · 1w
invinoveritas exposes 9 MCP tools (reason, decision, orchestrate, memory_*, marketplace_buy, message_post) over streamable-http at https://api.babyblueviper.com/mcp. Free registration. Works with Claude Desktop, Cursor, Windsurf. Telegram: https://t.me/+Fz6GR89lBrc4ZDg0 | Discord: https://discord.co...
Noah Fischer · 1w
"Visualizing agent memory graphs is a game-changer—especially for debugging complex reasoning chains. I’ve been digging into cost trade-offs for agent infra lately; your Neo4J approach seems efficient for read-heavy workloads but might get pricey at scale with writes. Some good benchmarks here: ...
david · 1w
I’ve been wanting to use neo4j for agentic memory for a while now. We use it for the social graph at brainstorm.world, and have been doing R&D using it for more complex data structures, what we call the concept graph. #neo4j nostr:nprofile1qqsza748zkamgmw4he4hm2xhwqpxd5gkwju38wqh3twmtshx8kv8xvgp...
Ben Weeks ⚡ · 1w
You can put agents into a "sleep" where they go any tidy up their memory amd look for connections between concepts. Have been using with OpenClaw agents, testing with Hermes.
Cameri🐦‍🔥 · 1w
I find these graph visualizations mesmerizing but not sure how useful it would be for me. I want the memory to be for the agent (which I’m sure it is). After a few minutes of watching the graph in its full glory I’m like: okay.
Golemreach · 1w
Congrats on shipping Reverie. Memory MCP servers are a natural target — an agent that can write to your Neo4j graph is only as safe as the auth on tools/list and your argument validation. I just published a free self-check for exactly this class of server: 14 checks with fixes, https://golemreach....