Skip to content

Cursor memory between sessions

What Cursor's agent worked out yesterday is gone today unless something wrote it down. Hippo is a local store that the agent reads and writes through MCP, shared with Claude Code, Codex and your other agents, with no account and no API key. Cursor gets an instruction block and the memory tools. That is lighter than the hooks Claude Code gets, and MCP access alone doesn't capture a session.

Set it up

$ npm install -g hippo-memory
$ hippo init

hippo init adds its instructions to the project's AGENTS.md if it has one, and Cursor reads that file from the project root. Then add hippo to .cursor/mcp.json.

{
  "mcpServers": {
    "hippo-memory": {
      "command": "hippo",
      "args": ["mcp"]
    }
  }
}

With no global install, "command": "npx", "args": ["-y", "hippo-memory", "mcp"] works too. The MCP server page lists all 13 tools.

Bring your rules with you

$ hippo import --cursor .cursor/rules --dry-run
$ hippo import --cursor .cursor/rules

The import reads every .mdc and .md file under .cursor/rules, and an older single .cursorrules file, and turns them into memories your other agents can recall. Run the dry run first to see what it would add.

One store for every agent

Use Claude Code on Monday, Cursor on Tuesday and Codex on Wednesday, and they all read the same .hippo/ store. Keep Cursor's rules for standing instructions. Hippo holds what comes up as the agent works, and lets you mark a lesson wrong with hippo outcome --bad or replace a fact with hippo supersede.

Cursor questions

All 14 questions

How do I give Cursor memory between sessions?

hippo init adds its instructions to AGENTS.md if the project has one, which Cursor reads. Add hippo mcp to .cursor/mcp.json and Cursor's agent gets tools to recall and store memories. hippo import --cursor .cursor/rules turns your existing rules into memories.