Give Cursor persistent memory across sessions

Cursor's agent is great inside a session, but close the window and it forgets your conventions, the decisions you made, and everything you told it about the project. Next session you re-explain your stack and coding rules all over again. This guide adds a memory that persists across Cursor sessions — no signup, no library, free.

Why Cursor forgets between sessions

Cursor keeps context within a chat, but there's no durable place for the agent to write a note to its future self. Nothing carries from one session to the next. The fix is an external memory the agent can read and write over MCP (Model Context Protocol) — which Cursor supports natively.

The short version

1. Open Corvid's home page and click once to create a private memory space. You get a personal URL with a secret token in it.
2. Add that one URL to Cursor's MCP config.
3. Now Cursor can remember facts and recall them in any future session.

Step by step: Cursor

Create a space on the home page and copy your URL. Then either use Settings → Cursor Settings → MCP → Add new MCP server, or edit the JSON directly. Global config lives at ~/.cursor/mcp.json; per-project config at .cursor/mcp.json in your repo:

{ "mcpServers": { "corvid": { "url": "https://corvid.perch-app.workers.dev/mcp?k=YOUR_TOKEN" } } }

Open the MCP settings pane and confirm corvid shows a green dot with its tools listed. Now in Agent mode you can say "remember that this repo uses pnpm and we never edit files in /generated", and next week in a fresh session "what are the rules for this repo?" — Cursor calls Corvid, finds the note, and answers with it.

What Cursor can do once it has memory

• remember — save a durable fact, convention, or architectural decision.
• recall — search memory at the start of a task so it picks up where you left off.
• list_recent — review the latest things it saved.
• forget — drop something that's no longer true.

Tip: put the durable stuff (conventions, decisions, gotchas) in Corvid so it survives across sessions and machines, and let per-project .cursor/rules handle always-on style rules. They complement each other.

Honest limitations

Corvid searches memory by keyword, so a lookup works best when it shares words with what was stored. Anyone who has your space token can read that space, so keep the URL private and don't store secrets in it. If you need encrypted, team-shared, or semantic-vector memory, a heavier tool may fit better — but for giving your own Cursor a memory that just works across sessions, this is the fastest path.

Prefer Claude Desktop or your own agent?

The same URL works in Claude Desktop and any MCP client that speaks streamable HTTP. Building your own agent? Skip MCP and call the plain HTTP API directly. Full setup notes are in the MCP guide.

Create a memory space →