Hi, I'm Daniel from Zep. I've integrated the Cursor IDE with Graphiti, our open-source temporal knowledge graph framework, to provide Cursor with persistent memory across sessions. The goal was simple: help Cursor remember your coding preferences, standards, and project specs, so you don't have to constantly remind it.<p>Before this integration, Cursor (an AI-assisted IDE many of us already use daily) lacked a robust way to persist user context. To solve this, I used Graphiti’s Model Context Protocol (MCP) server, which allows structured data exchange between the IDE and Graphiti's temporal knowledge graph.<p>Key points of how this works:<p>- Custom entities like 'Requirement', 'Preference', and 'Procedure' precisely capture coding standards and project specs.<p>- Real-time updates let Cursor adapt instantly—if you change frameworks or update standards, the memory updates immediately.<p>- Persistent retrieval ensures Cursor always recalls your latest preferences and project decisions, across new agent sessions, projects, and even after restarting the IDE.<p>I’d love your feedback—particularly on the approach and how it fits your workflow.<p>Here's a detailed write-up: <a href="https://www.getzep.com/blog/cursor-adding-memory-with-graphiti-mcp/">https://www.getzep.com/blog/cursor-adding-memory-with-graphi...</a><p>GitHub Repo: <a href="https://github.com/getzep/graphiti" rel="nofollow">https://github.com/getzep/graphiti</a><p>-Daniel
Super interesting and solves one of the main gripes I have for even the simplest tasks where I need to ask multiple times to make things consistent. How does it perform for mono-repos where different directories might have different standards (not ideal but unfortunate reality)?