3 ms·
You add some additional instructions to the Cursor rules here: https://github.com/getzep/graphiti/tree/main/mcp_server#integrating-with-the-cursor-ide https://g
by striking 2y ago
You add some additional instructions to the Cursor rules here: https://github.com/getzep/graphiti/tree/main/mcp_server#integrating-with-the-cursor-ide 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?
- roseway4 2y agoCorrect. The Graphiti MCP server, with the help of the agent, stores and retrieves preferences and requirements automatically without requiring rule changes.
- randall 2y agois this cursor specific or can i integrate with other things if im insane?
- roseway4 2y agoTotally 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/dbe21a1975b0747cd450ee3aa1b2c72b26f59230/mcp_server/graphiti_mcp_server.py#L37 https://github.com/getzep/graphiti/blob/dbe21a1975b0747cd450...
- rahimnathwani 2y agoBut you could tell cursor to update its rules automatically, no?
- dan_voronov 2y ago.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