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.
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
10 Comments
jasonjmcghee
What's the advantage over the built-in solution? (and before it, .cursorrules)
https://docs.cursor.com/context/rules-for-ai
adenta
This is exciting!
Glancing through the article, I can't tell, is this Cursor specific? Some of us are raw dogging VS Code with https://cline.bot, which supports MCP servers: https://cline.bot/mcp-marketplace.
Would love to try this out in Cline!
zman0225
This is so exciting!!!
mellosouls
This looks interesting but somewhat complicated or not obvious how to get going in a classic "Show HN" style.
The requirement for an OpenAI key may also be a little off-putting, or at least, could do with some indication of realistic costs; most Cursor users will likely need a significant motivation to add to the subscription they already have.
Don't get me wrong, this could be a really worthwhile addition to the LLM coding toolset but I think it needs some work on the presentation as to how to get quickly up and running.
stosssik
Looks super interesting. I hadn't heard of Graphiti before, but the idea of giving Cursor some kind of persistent, structured memory across sessions definitely sounds useful.
octernion
not obvious to me why this is an improvement of having the agent just update the rule files directly itself; i have it do that to my various AI-targeted readme files and it works great.
bbertelsen
One of the big problems I have with cursor is that it ignores the rules frequently. For example, working in the front-end it will sometimes totally ignore all the components that I have explicitly told it to use. Would this… fix that?
bfeynman
The over engineering here is commendable for something that provides most likely marginal value whilst still needing more api calls to summarize everything you do.
Garlef
It's there some way to control what gets updated in the database and how and when?
For example I'd like to be in control of the archtectural patterns and not let the LLM drive this.
randall
sweet!!