memory_write
Stores durable long-term memories across sessions and connected AI tools, preserving preferences, decisions, and facts for future recall. Use it for lasting context, not transient chatter or sensitive credentials.
Instructions
Store a long-term memory that persists across sessions and across every AI tool the user has connected to Mnemoverse. Suited to durable information: a stated preference, a decision, a fact about people, roles or project setup, a lesson learned; transient chatter that only matters this turn does not belong here. Never store passwords, API keys, payment data, MFA codes, government IDs, or health records. Behavior: outside shared rooms, a novelty gate refuses a write the embedder cannot tell apart from a memory already stored in the same domain, so the result tells you whether the memory was stored or refused. Write content as a self-contained statement that still makes sense when recalled out of context. To correct a memory you have checked is outdated, pass its memory_id in supersedes.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"content": "<content>"
},
"name": "memory_write"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | Namespace to organize memories (e.g. 'engineering', 'user:alice', 'project:acme'). Matched byte-for-byte — a leading space, a different case, or an invisible character opens a SEPARATE, permanent store, so reuse an exact name from memory_stats rather than retyping one. To write into a shared room, pass its address here instead (e.g. 'xroom:room_01ABC'). Find room addresses with memory_list_rooms. | |
| content | Yes | The memory to store as a self-contained statement, e.g. 'User prefers TypeScript strict mode' or 'Decided to deploy the API on Cloudflare Workers (2026-06)'. | |
| concepts | No | Key concepts for linking related memories (e.g. ['deploy', 'friday', 'staging']) | |
| supersedes | No | Pass the memory_id values of memories this write corrects or replaces. Use only for memories you have checked are outdated or wrong; the replaced memories stay recoverable with include_history. Not supported in shared rooms (xroom: domains). 1 to 32 distinct ids. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | The memory service's own explanation of this outcome, quoted as sent — when stored is false this is the ONLY statement of WHY, e.g. "Below importance threshold (0.047 < 0.1)". Ordinary text is preserved exactly; only control, bidi, zero-width, and repeated-whitespace characters are normalized before display, and the value is capped at 400 characters. Absent when the service sent no explanation, or when nothing remains after that normalization. | |
| stored | Yes | Whether the memory passed the novelty gate and was stored. | |
| memory_id | Yes | Identifier of the stored memory, or null when it was not stored. | |
| importance | No | Novelty score for this write (0-1): how much it adds over the nearest memories already saved in the same domain. Outside shared rooms, a write that scores below the service's importance threshold is not stored, and `reason` says why when the service sends one. The score is approximate and can read lower for non-English text. It is not a verdict on whether the memory was worth keeping. Absent when the service sent no score. | |
| superseded | No | The memory_id values this write replaced, in request order. Present only when the write replaced at least one memory. |