Cursor + PersistMemory
Memory for Cursor that outlives the conversation
Give Cursor memory of the decisions behind your codebase. Connect PersistMemory over MCP and it recalls why a thing was built that way, not just what the code says.
What Cursor forgets
Cursor reads your code, which tells it what the system does and never why. The reason you rejected the obvious approach, the constraint that forced the odd shape, the thing that broke last time — none of that is in the file, so it gets suggested again.
Ask why a module is structured that way and get the decision, not a guess from the code.
Constraints you recorded once stop being re-suggested every session.
Meeting notes and design docs become answerable from inside the editor.
Connecting it
Add this to .cursor/mcp.json and restart Cursor.
{
"mcpServers": {
"persistmemory": {
"url": "https://mcp.persistmemory.com/mcp",
"transport": "http"
}
}
}You sign in with your own account, and the connection is revocable from your dashboard. One live connection per platform: authorising Cursor again replaces the previous one rather than adding a second.