Direct answer
Persistent Memory MCP Server
Zambo stores memory server-side, so it survives new chats and new apps. Any AI connected to the Zambo MCP at https://zambo.dev/mcp can save a fact with one call and recall it in a later session, including a session in a different app: memory written in Claude can be recalled in Cursor, ChatGPT, or Grok, because the store lives on the server, not inside any one chat.
Updated October 20, 2026.
How it works
Most AI memory lives inside one product: a chat app remembers your chats, and a new app starts from zero. Zambo moves the store outside the apps. The MCP server holds the memory, keyed to your Zambo account, and any connected client reads and writes the same store over MCP. Starting a new chat does not clear it, switching from Claude to Cursor does not strand it, and the memory is available to the next session the moment it connects.
That makes memory a property of your setup rather than of one vendor. The clients change; the store, and the receipts for the work done with it, stay.
The calls
- memory_remember: save a fact, preference, decision, or piece of project context. Write it the way you would want to read it cold in a month: specific, dated where it matters, and free of anything only this chat would understand.
- memory_recall: pull memory back into a session. Recall at the start of a job, before asking the user to repeat context, and recall again when the topic changes.
A good working pattern is short: at the start of a session, recall; during the session, remember each decision and result worth keeping; at the end, remember the state of the job and what comes next. The next session, in any connected app, picks up from there.
Limits
Memory is only as good as what gets saved. A fact nobody remembered is not in the store, and a vague note recalls as a vague note, so the discipline of writing clear entries matters more than the storage. Recall returns what matches; it does not reason about which memory is still true, so when a fact changes, remember the new version and note that it replaces the old one. Memory also sits alongside, not instead of, the record of completed work: for what was actually done, the receipts for each call are the checkable layer, and anyone can verify one free at zambo.dev/verify.
For $0.99, a Day Pass covers 24 hours of full use. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders. Humans pay by PayPal or card through PayPal; agents pay with USDC on Base via x402.
Privacy
Memory entries are stored on Zambo's server under your account and are served only to clients connected with your access. Treat the store the way you would treat any synced notes: save context that helps future sessions work, and keep secrets, passwords, and one-time codes out of it entirely. Deleting is covered on the memory across tools page: when an entry should go, remove it from the store rather than writing a correction on top of it.
Honest limits
Server-side memory survives chats and apps only for clients connected to the same Zambo account; a client that was never connected cannot see it. The store keeps what your AI was told to remember, so it can hold mistakes an AI saved in good faith: recall is a starting point, not a source of truth, and important claims should still be checked against the receipts and the underlying work.
Frequently asked questions
What is a persistent memory MCP server?
A persistent memory MCP server stores memory outside the chat, on a server reached over MCP, so the memory survives new chats and new apps. Zambo works this way: any connected AI saves memory with memory_remember and recalls it with memory_recall, and the same store is shared across Claude, Cursor, ChatGPT, and Grok.
How is Zambo memory different from chat app memory?
Chat app memory belongs to one product and one account inside it, and it stays behind when you switch apps. Zambo memory lives in the MCP server, keyed to your Zambo account, so the store follows you across clients. A fact saved during a Claude session can be recalled in a Cursor session minutes later.
What should an AI save with memory_remember?
Save facts a future session would otherwise have to ask about: preferences, project decisions and their reasons, names and roles, the state of a job, and what happens next. Write each entry so it reads clearly cold, and when a fact changes, save the new version and note that it replaces the old one.
Does persistent memory replace receipts?
No. Memory holds context: what matters, what was decided, where things stand. Receipts hold the checkable record of work: each tool call saved at the moment it ran, verifiable by anyone at zambo.dev/verify. A healthy setup uses both, memory for continuity and receipts for proof of what was done.
How much does Zambo memory cost?
You can start on the free tier. A Day Pass costs $0.99 one time for 24 hours of full use. The Zambo Pass is $29 a month or $290 a year, and $19 a month for $ZAMBO holders. Humans pay by PayPal or card through PayPal; agents pay with USDC on Base via x402.