Memory your assistant keeps wherever you work
Assistants forget when the session ends, and what one tool remembers, the next tool cannot see. Pastepile stores memory as plain records your assistant reads and writes over MCP, so the same knowledge is there in every client that speaks the protocol.
The lock-in problem, plainly
Most assistant memory lives inside the vendor: useful while you stay, gone when you move, invisible to every other tool. Your architecture decisions, your conventions, yesterday's debugging conclusions become property of whichever chat window heard them.
Pastepile's answer is boring on purpose: memory is data you own, stored at addresses you can read. Anything an assistant saves here can be listed, searched, exported, and read by you in a browser, by a script over the REST API, or by a different assistant entirely.
How it works
- Your assistant connects through the Pastepile MCP server: one command locally, or a hosted endpoint with nothing installed. Any client that speaks the Model Context Protocol works: Claude Code, Cursor, Windsurf, and the rest of the MCP ecosystem. There is no vendor-specific integration to depend on, which is the point.
- Twelve tools cover the lifecycle: remember, recall, timeline, restore, plus the classic save, get, search, list, checkpoint, forget, a structured query language, and a memory-key export. Each one is documented in the MCP docs.
- Memory is versioned. An update is a new version, not an overwrite, and the timeline and restore tools walk it back. An assistant that clobbers its own notes stops being a data-loss incident.
- You can read everything yourself in the memory viewer, and export the whole namespace as one context package to carry elsewhere. Memory you cannot inspect or take with you is not really yours.
- Optional client-side encryption keeps memory content unreadable by us: the key stays with you, we store ciphertext. The trade is described honestly in the MCP security notes.
What to know before relying on it
- Private memory needs an API key, which comes with Pastepile Pro. The key defines the namespace: search and recall see only what was saved under it. Keyless remote saving is a trial that ends on September 8, 2026.
- Assistants rarely save unprompted. The setup that works is telling yours, in its own instructions, when to write things down; the assistant memory guide covers this.
- Unencrypted memory is stored as text we can read; do not have an assistant save credentials that way. Encrypted memory is opaque to us and to text search, by design.