Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Knowledge graphs are insanely good at giving agents human-like memory! Today, we're building an MCP-powered memory layer that can be shared across all your AI apps like Cursor, Claude Desktop etc. It's built using a real-time knowledge graph. 100% open-source and self-hosted.

Akshay 🚀

279,885 subscribers

156,446 views • 1 year ago •via X (Twitter)

Science & Technology Education

Anya Rossi• Live Now

Private livecam show

11 Comments

Akshay 🚀1 year ago

Tech stack: - @zep_ai's Graphiti as a memory layer - @neo4j to store the knowledge graph - @Docker to self host the MCP server Find all the code here:

Akshay 🚀1 year ago

@neo4j @Docker If you found it insightful, reshare with your network. Find me → @akshay_pachaar ✔️ For more insights and tutorials on LLMs, AI Agents, and Machine Learning!

Coral AI News2 years ago

Coral AI is the most powerful AI for documents. See the difference yourself:

Avi Chawla1 year ago

This is much needed functionality to work across multiple MCP hosts. Great way to solve it. Thanks Akshay

Akshay 🚀1 year ago

Absolutely! 💯 You don't have to switch context while switching apps!

Sumanth1 year ago

Memory layer that can be shared across all the AI apps. This is Incredible. Thanks for sharing Akshay, Great demo!

Akshay 🚀1 year ago

Thank You Sumanth! 🙏

guille1 year ago

The downside to using knowledge graphs is that there aren't any good graph databases on the market. Neo4j is expensive, power-hungry, and not very flexible, good open source alternatives are needed

ultravioleta🔺1 year ago

this is savage

Arindam Majumder 𝕏1 year ago

Wow! This is Amazing

Akshay 🚀1 year ago

Glad you liked it Arindam!

Related Videos

Agents forget everything after each task! Graphiti builds temporally-aware knowledge graphs for your AI agents. Integrating its MCP server with Claude/Cursor adds a powerful memory layer to all your interactions! 100% open-source with 9k+ stars!

Agents forget everything after each task! Graphiti builds temporally-aware knowledge graphs for your AI agents. Integrating its MCP server with Claude/Cursor adds a powerful memory layer to all your interactions! 100% open-source with 9k+ stars!

Avi Chawla

73,369 views • 1 year ago

Big update for Claude Desktop and Cursor users! Now you can connect all AI apps via a common memory layer in a minute. I used the Graphiti MCP server that runs 100% locally to cross-operate across AI apps like Claude Desktop and Cursor without losing context. (setup below)

Big update for Claude Desktop and Cursor users! Now you can connect all AI apps via a common memory layer in a minute. I used the Graphiti MCP server that runs 100% locally to cross-operate across AI apps like Claude Desktop and Cursor without losing context. (setup below)

Avi Chawla

122,824 views • 8 months ago

5 huge AI agents, MCP, and LLM updates today: 1. Mem0 just dropped OpenMemory MCP server that adds persistent memory across MCP clients. Create a shared memory layer with style, topics, emotions, etc. that works Claude, Cursor, Windsurf, and others. 100% local and opensource.

5 huge AI agents, MCP, and LLM updates today: 1. Mem0 just dropped OpenMemory MCP server that adds persistent memory across MCP clients. Create a shared memory layer with style, topics, emotions, etc. that works Claude, Cursor, Windsurf, and others. 100% local and opensource.

Unwind AI

63,243 views • 1 year ago

Building AI agents starts with a memory you can verify. The OriginTrail Decentralized Knowledge Graph (DKG) gives agents a verifiable memory layer built on structured knowledge you can trace back to its source. Brana Rakic explains 💬

Building AI agents starts with a memory you can verify. The OriginTrail Decentralized Knowledge Graph (DKG) gives agents a verifiable memory layer built on structured knowledge you can trace back to its source. Brana Rakic explains 💬

OriginTrail

25,946 views • 4 months ago

I added a Knowledge Graph to Cursor using MCP. You gotta see this working! Knowledge graphs are a game-changer for AI Agents, and this is one example of how you can take advantage of them. How this works: 1. Cursor connects to Graphiti's MCP Server. Graphiti is a very popular open-source Knowledge Graph library for AI agents. 2. Graphiti connects to Neo4j running locally. Now, every time I interact with Cursor, the information is synthesized and stored in the knowledge graph. In short, Cursor now "remembers" everything about our project. Huge! Here is the video I recorded.

I added a Knowledge Graph to Cursor using MCP. You gotta see this working! Knowledge graphs are a game-changer for AI Agents, and this is one example of how you can take advantage of them. How this works: 1. Cursor connects to Graphiti's MCP Server. Graphiti is a very popular open-source Knowledge Graph library for AI agents. 2. Graphiti connects to Neo4j running locally. Now, every time I interact with Cursor, the information is synthesized and stored in the knowledge graph. In short, Cursor now "remembers" everything about our project. Huge! Here is the video I recorded.

Santiago

155,514 views • 1 year ago

Traces, knowledge, and reasoning paths form a reliable source of truth for AI agents. 🤝 Charles Ivie, former Senior Graph Architect at Amazon Web Services, on why knowledge-backed traces are essential for trustworthy AI. 03:34 – Why data origin matters 07:17 – Interoperability and trusted knowledge 11:12 – Knowledge graphs as structured AI memory 16:09 – How combining graphs improves trust

Traces, knowledge, and reasoning paths form a reliable source of truth for AI agents. 🤝 Charles Ivie, former Senior Graph Architect at Amazon Web Services, on why knowledge-backed traces are essential for trustworthy AI. 03:34 – Why data origin matters 07:17 – Interoperability and trusted knowledge 11:12 – Knowledge graphs as structured AI memory 16:09 – How combining graphs improves trust

OriginTrail

12,528 views • 5 months ago

Open sourcing Dynamic Graph Memory by mem0. Memory is fundamental to human reasoning, shaping how we approach tasks and make decisions. At Mem0, we believe that AI agents & apps should reflect this principle. Our Dynamic Graph Memory emulates human memory, advancing AI agents toward more intelligent, human-like reasoning. This is a significant step forward in building AI that truly understands and interacts with the world like we do. All credit to Dev Khant Deshraj Yadav Prateek Chhikara for their countless nights spent on bringing this to life. Link:

Open sourcing Dynamic Graph Memory by mem0. Memory is fundamental to human reasoning, shaping how we approach tasks and make decisions. At Mem0, we believe that AI agents & apps should reflect this principle. Our Dynamic Graph Memory emulates human memory, advancing AI agents toward more intelligent, human-like reasoning. This is a significant step forward in building AI that truly understands and interacts with the world like we do. All credit to Dev Khant Deshraj Yadav Prateek Chhikara for their countless nights spent on bringing this to life. Link:

Taranjeet

51,129 views • 1 year ago

Supercharging Microsoft Microsoft Copilot with verifiable memory, powered by OriginTrail Decentralized Knowledge Graph!⚡️ With Model Context Protocol (MCP), agents can plug into the DKG to access verifiable knowledge, discover context & store trusted memory. Jurij Skornik demos ⤵️

Supercharging Microsoft Microsoft Copilot with verifiable memory, powered by OriginTrail Decentralized Knowledge Graph!⚡️ With Model Context Protocol (MCP), agents can plug into the DKG to access verifiable knowledge, discover context & store trusted memory. Jurij Skornik demos ⤵️

OriginTrail

49,297 views • 1 year ago

Knowledge graphs are infinitely better than vector search for building the memory of AI agents. With five lines of code, you can build a knowledge graph with your data. When you see the results, you'll never go back to vector-mediocrity-land. Here is a quick video:

Knowledge graphs are infinitely better than vector search for building the memory of AI agents. With five lines of code, you can build a knowledge graph with your data. When you see the results, you'll never go back to vector-mediocrity-land. Here is a quick video:

Santiago

397,989 views • 1 year ago

We’re excited to launch OpenMemory MCP, a private memory for MCP-compatible clients powered by mem0 Today, most AI assistants and dev tools operate without memory. You plan your roadmap in Claude, implement tasks in Cursor, but none of them know what the other did. Each tool operates in isolation, and your context disappears as soon as the session ends. OpenMemory MCP solves this. Built on the open Model Context Protocol (MCP), OpenMemory MCP runs 100% locally and provides a persistent, portable memory layer for all your AI tools. It enables agents and assistants to read from and write to a shared memory, securely and privately. Key capabilities: ✅Works across MCP clients like Cursor, Claude Desktop, Windsurf, Cline and more ✅Provides standardized memory operations (add_memories, search_memory, list_memories, delete_all_memories) ✅Stores data on your machine, fully private ✅Offers a centralized dashboard for visibility and control ✅Simple Docker-based setup with no vendor lock-in If you're building on MCP, OpenMemory MCP is the easiest way to add persistent, private memory to your clients with zero cloud dependencies and full local control. We’ve put together a short demo to show how it works Check it out in the links below 👇

We’re excited to launch OpenMemory MCP, a private memory for MCP-compatible clients powered by mem0 Today, most AI assistants and dev tools operate without memory. You plan your roadmap in Claude, implement tasks in Cursor, but none of them know what the other did. Each tool operates in isolation, and your context disappears as soon as the session ends. OpenMemory MCP solves this. Built on the open Model Context Protocol (MCP), OpenMemory MCP runs 100% locally and provides a persistent, portable memory layer for all your AI tools. It enables agents and assistants to read from and write to a shared memory, securely and privately. Key capabilities: ✅Works across MCP clients like Cursor, Claude Desktop, Windsurf, Cline and more ✅Provides standardized memory operations (add_memories, search_memory, list_memories, delete_all_memories) ✅Stores data on your machine, fully private ✅Offers a centralized dashboard for visibility and control ✅Simple Docker-based setup with no vendor lock-in If you're building on MCP, OpenMemory MCP is the easiest way to add persistent, private memory to your clients with zero cloud dependencies and full local control. We’ve put together a short demo to show how it works Check it out in the links below 👇

Taranjeet

471,767 views • 1 year ago

2️⃣ Graphiti MCP server Agents forget everything after each task. Graphiti MCP server lets Agents build and query temporally-aware knowledge graphs, which act as an Agent's memory! Check this👇

2️⃣ Graphiti MCP server Agents forget everything after each task. Graphiti MCP server lets Agents build and query temporally-aware knowledge graphs, which act as an Agent's memory! Check this👇

Avi Chawla

37,902 views • 1 year ago

RAG might already be becoming obsolete. A month ago, Andrej Karpathy dropped a simple GitHub gist called “LLM Wiki.” Now the comments section looks like the birth of an entirely new AI category. 5000+ stars later, developers are rapidly building: • persistent AI memory systems • self-maintaining knowledge bases • multi-agent research environments • contradiction detection engines • AI-native company operating systems • local-first memory architectures • graph-based reasoning layers • evolving second brains And the craziest part? Most of them were built in DAYS. Because the core idea is insanely powerful: Instead of AI repeatedly retrieving raw chunks like traditional RAG… …the model continuously maintains a living knowledge system. Not temporary context. Persistent synthesis. The shift sounds subtle until you realize what it changes: RAG: retrieve → answer → forget LLM Wiki: ingest → synthesize → evolve That one architectural difference is causing an explosion of experimentation right now. People are already building: • agent memory operating systems • AI-maintained engineering documentation • self-healing knowledge graphs • persistent research environments • conversational memory architectures • contradiction-aware wikis • context compression engines • machine-readable company systems The comments section alone feels like watching an ecosystem form in real time. One developer built deterministic contradiction detection using sheaf cohomology Another built “sleep consolidation” for AI memory systems inspired by human memory formation Another created persistent multi-agent vault conversations Another turned entire repositories into continuously maintained AI wikis Another built local-first memory systems with audit trails, provenance, graph exports, and MCP integration This is the important part: Karpathy didn’t launch a product. He introduced a pattern. And patterns are what create ecosystems. The same way: • transformers created modern AI • RAG created AI retrieval startups • agents created orchestration frameworks LLM Wikis may create persistent AI memory infrastructure. That’s why this moment feels different. For years, AI systems have been stateless. Now developers are trying to build systems that actually accumulate understanding over time. And once knowledge compounds instead of resetting… …the entire interface layer of AI changes. (Link in comments)

RAG might already be becoming obsolete. A month ago, Andrej Karpathy dropped a simple GitHub gist called “LLM Wiki.” Now the comments section looks like the birth of an entirely new AI category. 5000+ stars later, developers are rapidly building: • persistent AI memory systems • self-maintaining knowledge bases • multi-agent research environments • contradiction detection engines • AI-native company operating systems • local-first memory architectures • graph-based reasoning layers • evolving second brains And the craziest part? Most of them were built in DAYS. Because the core idea is insanely powerful: Instead of AI repeatedly retrieving raw chunks like traditional RAG… …the model continuously maintains a living knowledge system. Not temporary context. Persistent synthesis. The shift sounds subtle until you realize what it changes: RAG: retrieve → answer → forget LLM Wiki: ingest → synthesize → evolve That one architectural difference is causing an explosion of experimentation right now. People are already building: • agent memory operating systems • AI-maintained engineering documentation • self-healing knowledge graphs • persistent research environments • conversational memory architectures • contradiction-aware wikis • context compression engines • machine-readable company systems The comments section alone feels like watching an ecosystem form in real time. One developer built deterministic contradiction detection using sheaf cohomology Another built “sleep consolidation” for AI memory systems inspired by human memory formation Another created persistent multi-agent vault conversations Another turned entire repositories into continuously maintained AI wikis Another built local-first memory systems with audit trails, provenance, graph exports, and MCP integration This is the important part: Karpathy didn’t launch a product. He introduced a pattern. And patterns are what create ecosystems. The same way: • transformers created modern AI • RAG created AI retrieval startups • agents created orchestration frameworks LLM Wikis may create persistent AI memory infrastructure. That’s why this moment feels different. For years, AI systems have been stateless. Now developers are trying to build systems that actually accumulate understanding over time. And once knowledge compounds instead of resetting… …the entire interface layer of AI changes. (Link in comments)

Suryansh Tiwari

141,154 views • 1 month ago

Memory Store (Memory Store) gives your team and AI agents a shared company brain. Your team's knowledge & decisions are scattered across slack, emails, and people's heads. Memory Store turns them into a living wiki for your agents and teammates. Congrats on the launch, Ishita Jindal & Diwank Singh Tomer!

Memory Store (Memory Store) gives your team and AI agents a shared company brain. Your team's knowledge & decisions are scattered across slack, emails, and people's heads. Memory Store turns them into a living wiki for your agents and teammates. Congrats on the launch, Ishita Jindal & Diwank Singh Tomer!

Y Combinator

243,319 views • 1 month ago

Introducing the all new supermemory 💥 we killed the AI memory lock-in. A universal memory for all the apps you use: - MCP connect to Claude / Cursor / ChatGPT - Graph view of your life - Projects to organize your life free to use. $9/m for first 100 pro subs. demo below

Introducing the all new supermemory 💥 we killed the AI memory lock-in. A universal memory for all the apps you use: - MCP connect to Claude / Cursor / ChatGPT - Graph view of your life - Projects to organize your life free to use. $9/m for first 100 pro subs. demo below

Dhravya Shah

170,604 views • 11 months ago

Your AI agents can now explore knowledge infinitely. The new HyperGraph. Type a topic. Get a skill graph. Click any node to go deeper. Watch new concepts bloom in real time. Start with one idea. End with a complete knowledge base. Open source. Powered by Hyperbrowser.

Your AI agents can now explore knowledge infinitely. The new HyperGraph. Type a topic. Get a skill graph. Click any node to go deeper. Watch new concepts bloom in real time. Start with one idea. End with a complete knowledge base. Open source. Powered by Hyperbrowser.

Hyperbrowser

11,243 views • 3 months ago

Introducing GraphEngine — GraphAI’s Flagship Product An AI-native indexing and querying platform delivering real-time knowledge graphs and memory extension for large language models, agents, and applications. ✅ Closed Beta launches soon, giving developers and testers early access.

Introducing GraphEngine — GraphAI’s Flagship Product An AI-native indexing and querying platform delivering real-time knowledge graphs and memory extension for large language models, agents, and applications. ✅ Closed Beta launches soon, giving developers and testers early access.

GraphAI

47,857 views • 11 months ago

Stop prompt-stuffing yesterday’s context into your agent. Give it verifiable memory. 🕸️ When memory has provenance, agents can reuse it, audit it, and carry it across tools. Brana Rakic, Shaw (spirit/acc) (elizaOS), Ortecha | data made human & JoeVezz (LunarCrush 🌕™) break it down. 00:57 – What agents need to scale 05:45 – Social data, signals & real-time context 13:42 – Knowledge graphs as shared memory for AI agents 29:13 – Interoperability, trust & coordination

Stop prompt-stuffing yesterday’s context into your agent. Give it verifiable memory. 🕸️ When memory has provenance, agents can reuse it, audit it, and carry it across tools. Brana Rakic, Shaw (spirit/acc) (elizaOS), Ortecha | data made human & JoeVezz (LunarCrush 🌕™) break it down. 00:57 – What agents need to scale 05:45 – Social data, signals & real-time context 13:42 – Knowledge graphs as shared memory for AI agents 29:13 – Interoperability, trust & coordination

OriginTrail

13,293 views • 4 months ago

we built the world’s first self-installing API powered by claude code add memory to your AI agents in 5 mins with Hyperspell (YC F25) no human coding required

we built the world’s first self-installing API powered by claude code add memory to your AI agents in 5 mins with Hyperspell (YC F25) no human coding required

conor brennan-burke

29,355 views • 8 months ago

Cross-context Personal Knowledge Base with Social Graph🧠 Introducing Cross-context Personal Knowledge Base with Social Graph. Your Memory, Across Every Conversation Most AI forgets you the moment a chat ends. Teamily's Personal Knowledge Base remembers — across every group, every agent, and every context. Powered by your social graph, it connects the dots between your work, relationships, and ideas, so your AI always knows who you are, what you care about, and what happened before. No setup. No tagging. Just intelligence that grows with you. 🙌Try the prompt today: “visualize my knowledge base with social graph” #teamily #AI #Agent #KnowledgeBase #Social #SocialGraph

Cross-context Personal Knowledge Base with Social Graph🧠 Introducing Cross-context Personal Knowledge Base with Social Graph. Your Memory, Across Every Conversation Most AI forgets you the moment a chat ends. Teamily's Personal Knowledge Base remembers — across every group, every agent, and every context. Powered by your social graph, it connects the dots between your work, relationships, and ideas, so your AI always knows who you are, what you care about, and what happened before. No setup. No tagging. Just intelligence that grows with you. 🙌Try the prompt today: “visualize my knowledge base with social graph” #teamily #AI #Agent #KnowledgeBase #Social #SocialGraph

Teamily AI

13,287 views • 2 months ago

These 10 MCP servers are almost all you'll ever need. Curated after months of building. 1. DeepGraph MCP turns code repos into interactive knowledge graphs. Semantically search code functionalities, analyze dependencies, and explore direct relationships. 100% open-source.

These 10 MCP servers are almost all you'll ever need. Curated after months of building. 1. DeepGraph MCP turns code repos into interactive knowledge graphs. Semantically search code functionalities, analyze dependencies, and explore direct relationships. 100% open-source.

Unwind AI

36,934 views • 9 months ago