What's the advantage over the built-in solution? (and before it, .cursorrules)
You add some additional instructions to the Cursor rules here: https://github.com/getzep/graphiti/tree/main/mcp_server#inte...
I think the difference is that Cursor doesn't update its rules automatically as you work, while this might?
.cursorrules and other files that are added as system instructions in Cursor are just files, meaning the agent can edit them easely - you can tell it from the chat to add something to a rule and it will do it.
You are also wrong that it cannot do this automatically: if you add to the system instruction to record all important decisions in .cursorrules, it will record them there. automatically
Correct. The Graphiti MCP server, with the help of the agent, stores and retrieves preferences and requirements automatically without requiring rule changes.
is this cursor specific or can i integrate with other things if im insane?
Totally not Cursor-specific. Any MCP Client can be used. You may want to use different entity types that make more sense for your use case: https://github.com/getzep/graphiti/blob/dbe21a1975b0747cd450...