SAE4U Memory
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAE4U_MEMORY_HOME | No | Override the data directory (default ~/.sae4u-memory) | |
| SAE4U_MARKDOWN_ROOTS | No | Colon-separated list of markdown roots that recall() should search. Defaults to all Claude Code auto-memory dirs plus SAE4U_MEMORY_HOME. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberA | Save a fact, observation, or piece of context to persistent memory. Use this when you learn something important about the user, their projects, their preferences, or anything else worth recalling in future sessions. Args: text: The fact or observation to remember. category: Optional category — "user", "feedback", "project", "reference", "general". Defaults to "general". |
| recallA | Search persistent memory for relevant facts. Scans TWO corpora by default and merges results:
Use this at the start of any substantive conversation to pull in prior context, feedback rules, project state, and recent session observations. Args: query: Search terms. Empty string returns most recent entries. limit: Max results per source (default 5). category: Optional filter (SQLite only). sources: "all" (default), "sqlite", or "markdown". |
| list_memoriesB | List stored memories, optionally filtered by category. Args: category: Filter by category (user/feedback/project/reference/general). limit: Max results to return. |
| forgetA | Delete a memory by its id. Use this when a stored fact turns out to be wrong or outdated. Args: memory_id: The id of the memory to remove. |
| journalA | Write an end-of-session journal entry. Use this at the end of a significant conversation to record what happened, decisions made, and what to remember for next time. Journals are stored in ~/.sae4u-memory/journals/YYYY-MM-DD.md for human reading. Args: text: The journal entry text. |
| get_personaA | Return the current persona + user context. This gives the AI its identity and what it knows about the user. Call this at session start to load full context. |
| recent_journalsA | Retrieve recent journal entries. Args: days: Number of days back to search (default 7). |
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 7 tools
Each tool has a clear, distinct purpose: create (remember), read (list_memories, recall, get_persona, recent_journals), delete (forget), and journaling (journal). No two tools appear to do the same thing, even list_memories and recall are differentiated by browsing vs. searching.
Names mix patterns: verbs alone (forget, recall, remember, journal), verb+noun (get_persona, list_memories), and adjective+noun (recent_journals). While still readable, the lack of a uniform convention introduces minor confusion.
7 tools cover the essential operations for a memory system—create, read, delete, and journaling—without being excessive. Each tool feels justified and contributes to the server's purpose.
Core CRUD is mostly present, but update is missing (memories and journals can only be overwritten by deletion+recreation). This is a minor gap that agents can work around, so the surface is nearly complete.