Show HN: Cursor IDE now remembers your coding prefs using MCP
getzep.comHi, 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.
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.
Key points of how this works:
- Custom entities like 'Requirement', 'Preference', and 'Procedure' precisely capture coding standards and project specs.
- Real-time updates let Cursor adapt instantly—if you change frameworks or update standards, the memory updates immediately.
- Persistent retrieval ensures Cursor always recalls your latest preferences and project decisions, across new agent sessions, projects, and even after restarting the IDE.
I’d love your feedback—particularly on the approach and how it fits your workflow.
Here's a detailed write-up: https://www.getzep.com/blog/cursor-adding-memory-with-graphi...
GitHub Repo: https://github.com/getzep/graphiti
-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)? I'm not actually sure. Using Cursor Rules, you may be able to instruct the agent to be explicit as to which project a memory is related to. And do the same with retrieval i.e. tell the agent to rerank search results by distance from the project node. The Tools are all there for the agent to use. Compliance likely depends on the Cursor Rules and the model used.