persistent-memory-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PERSISTENT_MEMORY_DIR | No | Directory of the memory store. Leave empty to use the platform data folder. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Long-term memory with provenance. Search it before answering about earlier facts, decisions or procedures, and cite the artifact_id of what you rely on. Store something only when the user states or confirms it; use kind 'hypothesis' for guesses. When a correction or a withdrawal is asked for, use memory_correct or memory_withdraw rather than storing a contradicting fact. If a result carries memory_notices, stop relying on those artifacts, including what you said from them earlier.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_searchA | Find stored facts, decisions and procedures by keywords. Use it before answering about anything the user said or decided earlier. Returns only current, valid versions, each with its text, kind, artifact_id and exact ref; withdrawn, superseded and expired versions are left out, and an empty list means nothing valid matches. Read-only. To re-read one version you already hold, use memory_read. |
| memory_readA | Re-read one exact version you got from memory_search or a write, for example before relying on it again later in a conversation. Returns its text if it is still valid; otherwise allowed is false and reason and state say why (superseded, withdrawn, expired), with no text. Read-only. To look for something, use memory_search. |
| memory_rememberA | Store a new fact, decision, document or procedure the user stated or confirmed, as a source. Do not use it for your own conclusions (memory_derive), for lessons after a task (memory_learn), or to change something already stored (memory_correct). Returns artifact_id and ref. Sending the same source_id with the same text again changes nothing; with a different text it is refused with version_conflict. |
| memory_deriveA | Store a summary, conclusion or procedure you built from entries already in memory, linked to the exact versions it came from. Use it instead of memory_remember whenever the text depends on stored entries: if one of them is later corrected or withdrawn, this artifact stops being served and sessions that saw it are notified. Returns artifact_id and ref. |
| memory_correctA | Replace an artifact's text when the user corrects it, keeping its history. Only applies if expected_version is still its current version; otherwise it is refused with version_conflict, and you search again. Metadata you leave out is kept. Whatever was derived from the old version stops being served and its readers are notified. To remove something entirely, use memory_withdraw. |
| memory_explainA | Explain why an artifact is or is not served: its state, its versions, what it was derived from and what depends on it. Metadata only, never text. Use it when a search leaves out something the user expects, or before a correction. Read-only; unknown_artifact if it does not exist. Give artifact_id or ref. |
| memory_plan_withdrawalA | Preview a withdrawal: list every version that memory_withdraw would stop serving, the artifact and everything derived from it, without changing anything. Use it to show the user the consequences before withdrawing. |
| memory_withdrawA | Stop serving an artifact the user says is wrong, outdated or must be forgotten, together with everything derived from it; sessions that saw them are notified. The text is not physically erased and the history keeps the reason. Run memory_plan_withdrawal first when the user should see what it blocks. To replace a text with a better one, use memory_correct instead. |
| memory_learnA | After a task, store the lesson drawn from it, with the task trace and the feedback it got kept as its provenance. Only the lesson is returned by searches; withdrawing the trace or the feedback stops serving the lesson. For a fact the user states, use memory_remember. |
| memory_noticesA | List the artifacts this session was shown that have since been withdrawn, invalidated or superseded, so you stop relying on them and on what you said from them. Each is reported once. Other tool results already carry new notices as memory_notices; call this when you need to check explicitly, for example before a final answer. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a sharply distinct role, and the descriptions explicitly route the agent between them (remember vs derive vs learn, search vs read, correct vs withdraw vs plan_withdrawal). The overlap-prone pairs (search/read, explain/plan_withdrawal) are separated by clear read-only vs mutating and metadata vs preview boundaries. No two tools appear to do the same thing.
All names share a consistent memory_ prefix with mostly verb second elements (search, read, remember, correct, explain, derive, learn, withdraw). Minor deviations: memory_notices is a noun rather than a verb, and memory_plan_withdrawal is a verb_noun compound while others are single verbs. Still highly predictable overall.
Ten tools is well within the sweet spot and each one earns its place: three write paths, two read paths, a correction path, a withdrawal path with a safe preview, plus explain and notices for lineage/notification. Nothing feels redundant or padding.
The lifecycle is well covered: create (remember/derive/learn), read (search/read), update (correct), soft-delete (plan_withdrawal/withdraw), and introspection (explain/notices). Minor gaps: no enumeration/list tool to browse artifacts without keywords, and no restore/undo path for a withdrawal (by design, since text is retained, but there is no way to re-serve it).