Memento
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMENTO_ROOT | No | Optional root directory for the memory folder. If not set, the server resolves it per tool call: nearest .memento.toml walking up from the working directory, or defaults to docs/memory under the working directory. |
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 |
|---|---|
| read_allA | Load the whole project memory: every markdown file in the memory folder, concatenated, each prefixed with a marker. |
| searchA | Case-insensitive substring search over entry titles, bodies, tags and
status. Optional |
| writeA | Write a new memory entry. type: decision | contract | task | log | evaluation (unknown types get their own {TYPE}S.md file). Appends to the matching file with a fresh sequential id and Status: active. |
| updateA | Update an existing entry by id (e.g. "dec-001"). Only the fields you pass are changed; the rest of the file is preserved byte-for-byte. |
| logA | Append a session log entry. The first line of body becomes the title. |
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 5 tools
The tools are mostly distinct: read_all and search differ in scope (full dump vs targeted lookup), and write/update/log each have clear intents. The only minor ambiguity is write with type 'log' overlapping the dedicated log tool, but descriptions sufficiently clarify the difference.
All tool names are imperative verbs (search, write, update, log, read_all), which makes them predictable. The slight deviation is 'read_all' with an underscore suffix versus the single-word names of the other tools, but the pattern is still coherent.
Five tools is well-scoped for a memory-management server. Each tool covers a distinct core operation—full read, search, create, update, and session logging—without bloat or trivial fragmentation.
The toolset covers reading, searching, writing, updating, and logging, which handles the main memory lifecycle. There is no explicit delete, but update can set status to inactive, so the gap is minor and workaroundable.